Difference between revisions of "Sprint Zero"

From CNM Wiki
Jump to: navigation, search
Line 1: Line 1:
 
In some [[Agile methodology|Agile methodologi]]es such as [[Agile Scrum]] and [[CNM Agile]], [[Sprint Zero]] is the name of a special [[project]] undertaken to plan a bigger project, which consists of several [[iteration]]s called [[Sprint]]s.
 
In some [[Agile methodology|Agile methodologi]]es such as [[Agile Scrum]] and [[CNM Agile]], [[Sprint Zero]] is the name of a special [[project]] undertaken to plan a bigger project, which consists of several [[iteration]]s called [[Sprint]]s.
  
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-shipable 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.
  
 
*https://www.quora.com/How-do-you-define-a-zero-sprint-in-the-scrum-life-cycle
 
*https://www.quora.com/How-do-you-define-a-zero-sprint-in-the-scrum-life-cycle

Revision as of 17:23, 9 April 2020

In some Agile methodologies such as Agile Scrum and CNM Agile, Sprint Zero is the name of a special project undertaken to plan a bigger project, which consists of several iterations called Sprints.

In Scrum's definitions, every Sprint is an attempt to produce a potentially-shipable 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.