Skip to main content

Sprint 0

Last post 08:11 am May 30, 2016 by Kevin Verhaegen
7 replies
06:22 pm April 6, 2016

I am confused about Sprint zero. What is it used for? Any accountability from any of the Scrum Team?

Also, how best to determine the length of the sprint - proportional to the work, long enough to make sure the team can deliver, determined during the planning?


12:58 pm April 7, 2016


Hello,
As far as I know, there is no Sprint 0.

For all purposes, you should start with Sprint 1 when you have a minimal set of product backlog items to work on.
Sprint length should be finalized after discussions with the product owner I reckon, as the risk should be acceptable to him.
Of course, the same should also be discussed with the development team.


11:12 am April 8, 2016

There is a first sprint, with a potentially shippable (very small) increment.
You can name it sprint 0 ; sprint 1 ; sprint alpha ; sprint john... But it is a sprint


03:08 pm May 24, 2016

Hi,

Still I have some confusion on Sprint 0.

While reading some articles in net, a few are saying something on sprint zero similar to backlog refining. Do we need to rely on those information?

As per their explanation, its a sprint or duration to prepare a designable product back log for dev team or detailed estimation. When reading scrum guide or Sbok, there is nothing related to Sprint Zeros other than normal sprints. However any specific task or process we need to do for Spint zero from development team or product owner perspective? Could you please advise?

Thanks,
Arun P


03:38 pm May 24, 2016

We do not use the term "Sprint 0." You are referring to the time before Sprint 1, used to prepare an initial Product Backlog, build a Development Team, assign Product Owner and Scrum Master roles, build an initial development environment, etc.

It is not Sprint because it does not result in potentially releasable software. It's just the startup period. You should not spend more than a few weeks in this startup period before starting Sprint 1.

Best regards,
Mark Noneman
Professional Scrum Trainer


05:50 am May 29, 2016


Posted By Mark Noneman on 24 May 2016 03:38 PM
We do not use the term "Sprint 0." You are referring to the time before Sprint 1, used to prepare an initial Product Backlog, build a Development Team, assign Product Owner and Scrum Master roles, build an initial development environment, etc.

It is not Sprint because it does not result in potentially releasable software. It's just the startup period. You should not spend more than a few weeks in this startup period before starting Sprint 1.



Totally agree with it.
The purpose of a sprint is to deliver a piece of functionality.
If there is not such a thing, this is not a sprint, but just a preparation (before your first sprint) to be ready to implement and deliver your first(s) functionality(ies).


01:22 am May 30, 2016


This question has been asked multiple times, I would redirect it to Scrum Guide which says

"The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, usable, and potentially releasable product Increment is created"

Though I don't mind starting my Sprint with any number, even negative, I know it looks silly.


08:11 am May 30, 2016

When looking at Scrum, there is no definition such as Sprint 0 or Sprint 1. You can name them ofcourse, but if you get a question about this, the answers should be "Scrum does not define a Sprint 0 or Sprint 1".


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.