Difference between revisions of "Sprint Zero"
| Line 1: | Line 1: | ||
| − | In [[CNM Agile]], [[Sprint Zero]] is a set of activities undertaken before an [[CNM Agile Sprint]] takes place. Many practitioners of [[Agile Scrum]] use the term, ''Sprint Zero'', for a special [[project]] undertaken to prepare and plan for a bigger project, which commonly consist of several [[iteration]]s called [[Sprint]]s. However, [[Agile Scrum]] doesn't officially recognize that term | + | In [[CNM Agile]], [[Sprint Zero]] is a set of activities undertaken before an [[CNM Agile Sprint]] takes place. Many practitioners of [[Agile Scrum]] use the term, ''Sprint Zero'', for a special [[project]] undertaken to prepare and plan for a bigger project, which commonly consist of several [[iteration]]s called [[Sprint]]s. However, [[Agile Scrum]] doesn't officially recognize that term. If a [[Sprint]] is defined as an attempt to produce a product increment that is potentially shippable, ''Sprint Zero'' is not a [[Sprint]]. The internal team, not a customer, is the only consumer of ''Sprint Zero'' results. |
| − | In Scrum's definitions, | + | In Scrum's definitions, , 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 19:26, 9 April 2020
In CNM Agile, Sprint Zero is a set of activities undertaken before an CNM Agile Sprint takes place. Many practitioners of Agile Scrum use the term, Sprint Zero, for a special project undertaken to prepare and plan for a bigger project, which commonly consist of several iterations called Sprints. However, Agile Scrum doesn't officially recognize that term. If a Sprint is defined as an attempt to produce a product increment that is potentially shippable, Sprint Zero is not a Sprint. The internal team, not a customer, is the only consumer of Sprint Zero results.
In Scrum's definitions, , 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.cleveroad.com/blog/software-development-process
- https://www.scrum-breakfast.com/2011/04/how-we-do-sprint-zero.html
- https://dzone.com/articles/antipattern-of-the-month-sprint-zero
- https://www.wiliam.com.au/wiliam-blog/sprint-zero-kicking-off-a-scrum-project-the-right-way
- https://www.scrum.org/resources/blog/scrubbing-sprint-zero
- https://manifesto.co.uk/scrum-practice-sprint-zero/
- https://www.luxoft.com/blog/vmoskalenko/the-power-of-sprint-zero/
- https://www.infoq.com/news/2008/09/sprint_zero/
- https://www.mountaingoatsoftware.com/blog/sprint-zero-a-good-idea-or-not
- https://www.bmc.com/blogs/sprint-zero/
