"Non-Functional" Stories
AllyPerformance OptimizationPerformance, scalability, and stability—so-called non-functional requirements—should be scheduled with stories too. Be sure that these stories have precise completion criteria. See Performance Optimization for more.
Group items tagged
A Kanban System for Software Engineering - 0 views
Crisp's Blog » One day in Kanban land - 0 views
Lean-Agile Software Development: The Kanban Kick-start Field Guide now available! - 0 views
-
The Kanban Kick-start Field Guide is now available! Concentrating experience from kick-starting 50+ teams #kanban http://t.co/B4Pf3s96OZ
Lean Software Development - 0 views
Priming Kanban - 0 views
Cynefin 101 - An Introduction - 1 views
James Shore: The Art of Agile Development: Stories - 0 views
-
-
Spike Stories AllySpike SolutionsSometimes programmers won't be able to estimate a story because they don't know enough about the technology required to implement the story. In this case, create a story to research that technology. An example of a research story is "Figure out how to estimate 'Send HTML' story". Programmers will often use a spike solution (see Spike Solutions) to research the technology, so these sorts of stories are often called spike stories.
Manifesto for Agile Software Development - 0 views
Frequency Reduces Difficulty - 0 views
The New Methodology - 0 views
Klaus Leopold: Kanban and its flight levels - 0 views