What is the purpose of Sprint Zero?Sprint Zero is often used to mean 'getting ready for the first sprint.' Some Scrum coaches don't like the term because every sprint should produce an increment of value for the customer or user. A sprint 0 which creates say, artifacts like a design document or development environment, violates this rule, because such artifacts have no value for the customer or user.
A colleague of mine argued that during Sprint Zero, the team implements the most important features from the product backlog with the object of determining the team's velocity. I disagreed, because we have the velocity from previous sprints/projects. So could you help me to understand clearly what is Sprint 0 about and when and why do we need it? I really appreciate your helps and articles. Thank you!
Still there are some things you need to have ready before you can do your first sprint planning:
- You must have the roles identified (Product Owner, ScrumMaster, Team).
- You must have an initial product backlog (and you probably should have a product vision).
- Enough of the product backlog must be estimated and prioritized that the team can pick a reasonable amount of high value work from the backlog in the first Sprint Planning.
- You might need to train your Product Owner and Team on Scrum.
- the sprint length
- the initial Definition of Done.
What does not come into 'sprint zero'? Creating the development environment, test environment, high level design or other artifacts, and any development or testing. Actual work related to the project (as opposed to getting ready to do Scrum) gets prioritized in the Product Backlog, then is agreed upon during the Sprint Planning 1, and must produce some increment of customer value.
I wrote previous about my experience with a Sprint Zero. I hope the above and the blog entry are helpful!