The Concept and Execution of Sprint Zero — Clearly Agile – Debunking Sprint Zero myths
In this post I want to deal with a very special number that some teams use in numbering their sprints–zero. The concept of a “sprint zero” has become popular with some teams and so it is important to consider whether or not this is a good idea. First, let’s agree on the basic premise of “sprint zero. For example, a team needs to be assembled.
That may involve hiring or moving people onto the project. Sometimes there is hardware to acquire or at least set up. Many projects argue for the need to write an initial product backlog even if just at a high level during a sprint zero. One of the biggest problems with having a sprint zero is that it establishes a precedent that there are certain sprints or sprint types that have unique rules. Teams doing a sprint zero, for example, will dispense with the idea of having something potentially shippable at the end of that sprint.
How can they have something potentially shippable after all if the goal of the sprint is to assemble the team that will develop the product? I find that many of these things that can be used to argue for the need for a sprint zero are really best thought of as things that happen in what I call the project before the project. Before a development project begins, there is often a project to decide if there should be a development project.
Before a company begins a major new initiative, someone has to think about whether that initiative should be undertaken at all. Since Scrum works well as a general purpose project management framework, it can be used to manage the work of this project-before-the-project. During this project-before-the-project, the early team members perhaps just a future product owner can work toward creating an initial product backlog, finding or hiring team members, setting up the technical environment, and so on.
I find it helpful to think of this work as a project of its own because it is not hard to imagine this work taking longer than one sprint, the special sprint zero.
What does a team using a sprint zero call their second sprint if they need one to do whatever work they’ve used to justify the special type of sprint? Is it sprint 0. I wrote more about this last topic–staying true to the principles of Scrum on a project-before-the-project– here.
Sweeping these deliverables under the rug through the “Sprint Zero” mechanism is a way to side-step the need to educate the organization, but it ultimately cheats stakeholders and the team out of the full benefits of a transparent process.
Mind that Scrum talks about potentially shippable increments PSI as opposed to potentially shippable code! Of course you can ship code, but you can ship other things as well. For example, a product-vision document could be a shippable increment. Sprints with the goal do gain insight are often called Exploration Sprints. They are not unusual. In general, the idea of the shippable increment is to make you define a clear-cut goal for your iteration. That’s the only way to make your progress measurable.
You cannot measure your progress on the task “understanding the problem domain”, but you can measure the progress on creating a document that contains the product vision. Because in the latter case you can discuss the result and find out whether it’s acceptable or not. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Start collaborating and sharing organizational knowledge.
Create a free Team Why Teams? Learn more about Teams. Can we have a Sprint Zero with no deliverable code? Ask Question. Asked 8 years, 7 months ago. Modified 8 years, 7 months ago. Viewed 2k times. Improve this question. Ashok Ramachandran Ashok Ramachandran 11k 1 1 gold badge 19 19 silver badges 49 49 bronze badges. Add a comment.
Sorted by: Reset to default. Highest score default Date modified newest first Date created oldest first. Typically not. Can I adapt Scrum to fit my needs?
Sure – but it wouldn’t be Scrum. Improve this answer. Remaining true to Scrum framework, the answer would be NO. Which is why Mike Cohn calls this portion a project before the project : During this project-before-the-project, the early team members perhaps just a future product owner can work toward creating an initial product backlog, finding or hiring team members, setting up the technical environment, and so on.
Even the concept of Sprint Zero is debatable amongst the founding fathers of Agile, as Alistair Cockburn stated : I have a sneaking feeling that someone was pressed about his use of Scrum when he did something that had no obvious business value at the start, and he invented “Oh, that was Sprint Zero! Aziz Shaikh Aziz Shaikh 3, 23 23 silver badges 40 40 bronze badges. Sprint Goal Sometimes, the drive to have a “Sprint Zero” seems like a need to have a tool-chain or architectural sprint without a concrete deliverable.
For example, the Sprint Goal of the first sprint could be something like: Install the development infrastructure needed to kick-start the project. User Stories and Sprint Review A literal interpretation of the Sprint Review process seems to make non-feature stories a no-no.
For example, your team’s first Sprint Review could certainly demonstrate developer-facing deliverables such as: The status screen of the project’s continuous integration server. The web interface for the new source control system. A live demo of “Hello, World! Todd A. Jacobs Sven Amann Sven Amann 4 4 silver badges 5 5 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown.
One moment, please – A Free PDF to Help You Choose the Approach
is it OK to have a Sprint 0 with no deliverable code? Remaining true to Scrum framework, the answer would be NO. Can you time-box the Sprint 0? If the answer is no then you would be violating two important factors of Scrum framework, first time-boxing and the second potentially deliverable code at the end of each sprint. Aug 15, · Possible SPRINT 0 Deliverable: Activities listed below will make the team ready for the upcoming Sprints and mainly Sprint 1 &2. This is . Sprint Zero Boilerplate. Sprints should have defined deliverables in the form of Backlog Items and Sprint Zero is no different. Some items will need to be project-specific, but many will be common from one project to the next. We build our list of Backlog Items around the following list: As a Scrum Team, we need to;.
Sprint 0 is The Best Way to Prepare Your Agile Product Team for Sprint 1 – DSRUPTR – 4 Tips and Tricks for Distributed Teams
Feb 26, · Sprint zero is usually claimed as necessary because there are things that need to be done before a Scrum project can start. For example, a team needs to be assembled. That may involve hiring or moving people onto the project. Sometimes there is hardware to acquire or at least set up. Many projects argue for the need to write an initial product. Mar 11, · Sprint Zero Goals. The primary goal of a Sprint Zero is the same as it is for a Scrum Sprint that is production. On the other hand, a Sprint Zero is not required to carry out as much heavy software development as a Scrum Sprint would. As previously stated, teams participating in Sprint Zero should keep it light. More specifically, the following should be the . In this approach, the deliverables of a Sprint Zero should be as follows: Infrastructure set up, product backlog creation, architecture planning, test plan preparation, story mapping, prototyping, design, tests validation, few first lines of code;.