What is the importance of Sprint 0?

1.	What is the importance of Sprint 0?
Answer» Sprint 0 is a concept that team needs some time to settle down before delivering actual value to the customer from sprint 1. But it has been misused a lot LATELY as an excuse to put everything in place then go for sprints. So essentially, the misuse is LIKE doing waterfall in Agile projects. The correct way of doing sprint 0 is when the REQUIREMENTS are very VAGUE that no user story can be started off or the TECHNOLOGY is completely new for the team or the project is so complex that there needs to be a dedicated time for product discovery. In such cases, sprint 0 should be allowed where team resolves these issues and is not bound to deliver any value.

Answer»

Sprint 0 is a concept that team needs some time to settle down before delivering actual value to the customer from sprint 1. But it has been misused a lot LATELY as an excuse to put everything in place then go for sprints. So essentially, the misuse is LIKE doing waterfall in Agile projects.

The correct way of doing sprint 0 is when the REQUIREMENTS are very VAGUE that no user story can be started off or the TECHNOLOGY is completely new for the team or the project is so complex that there needs to be a dedicated time for product discovery. In such cases, sprint 0 should be allowed where team resolves these issues and is not bound to deliver any value.

Discussion

No Comment Found

Related InterviewSolutions

What are the essential engineering practices when scaling Scrum across multiple product development teams?
How do you manage risks in Scrum projects?
How would you prepare to kick-off transitioning to Scrum? How would you create the first Scrum team?
How do you introduce Scrum to senior executives of your company?
What do you recommend a newly formed Scrum team works on first?
What’s the 2 pizza theory?
What is the biggest challenge you faced in your project while handling the Scrum team members?
Share your experience as a Scrum Master/Product Owner/Agile team member and what were your primary responsibilities?
What is the role of Sashimi in Scrum methodology?
Share some examples from your current or previous projects where you increased the chances of delivering a high value product and how you did it?