Difference between revisions of "Sprint Zero"

From CNM Wiki
Jump to: navigation, search
(Created page with "In Scrum's definitions, every Sprint is an attempt to produce a potentially-shippable product increment, no matter how small. Every Sprint contains a combination of analysis,...")
 
Line 1: Line 1:
 +
In [[Agile methodology|Agile methodologi]]es, [[Sprint Zero]] is the name of a special [[project]] undertaken to plan a bigger project called [[Sprint]].
 +
 
In Scrum's definitions, every Sprint is an attempt to produce a potentially-shippable product increment, no matter how small. Every Sprint contains a combination of analysis, design, infrastructure, development, testing, and integration. Therefore, the common dysfunction called "Sprint Zero" is actually a contradiction in terms. Companies (and misinformed consultants and trainers) use this as a way to avoid changing waterfall habits.
 
In Scrum's definitions, every Sprint is an attempt to produce a potentially-shippable product increment, no matter how small. Every Sprint contains a combination of analysis, design, infrastructure, development, testing, and integration. Therefore, the common dysfunction called "Sprint Zero" is actually a contradiction in terms. Companies (and misinformed consultants and trainers) use this as a way to avoid changing waterfall habits.
  

Revision as of 16:02, 9 April 2020

In Agile methodologies, Sprint Zero is the name of a special project undertaken to plan a bigger project called Sprint.

In Scrum's definitions, every Sprint is an attempt to produce a potentially-shippable product increment, no matter how small. Every Sprint contains a combination of analysis, design, infrastructure, development, testing, and integration. Therefore, the common dysfunction called "Sprint Zero" is actually a contradiction in terms. Companies (and misinformed consultants and trainers) use this as a way to avoid changing waterfall habits.