Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Is sprint 0 time-boxed?
Last Post 04 Jun 2013 10:58 AM by Avinash Swami. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Chong Lim
New Member
New Member
Posts:1
Chong Lim

--
30 May 2013 05:31 AM
    Logically it does not seem like it is, but some people claim it should be? So, is it formally a time-boxed event?
    Dominik Maximini
    New Member
    New Member
    Posts:64
    Dominik Maximini

    --
    30 May 2013 07:35 AM
    Hi Buatapa,

    there is nothing such as a "Sprint 0". The very nature of a Sprint is that it is timeboxed to not more than 30 days and that it delivers a potentially shippable product increment. If you conduct a "Sprint 0" as some sort of non-timeboxed thing to produce something of 0 value (like sketching the architecture), you are not doing Scrum even though you might use the vocabulary.

    If you have to do some sort of "project preparation", call it just that. If you want to save hussle and money, timebox it to 2 weeks, never more than 4 weeks. Anything else is a waste of precious energy and resources.
    Luis Javier Peris Morillo
    New Member
    New Member
    Posts:15
    Luis Javier Peris Morillo

    --
    31 May 2013 06:55 AM
    Question exam preparation and manual response.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1575
    Ian Mitchell

    --
    31 May 2013 09:56 AM
    As Dominik says, in Scrum there is no recognition of Sprint Zero. In practice the term tends to be used for early Sprints that never find their stride, or for which Scrum components like a Product Backlog, Scrum Master, or Product Owner have not yet been secured.

    A Sprint Zero is usually seen retrospectively. Few teams plan to have one, so it is rarely time-boxed. A simple, WIP limited Kanban of project set-up tasks is often better than trying (and failing) to use Scrum in a precocious manner.
    Joshua Partogi
    Basic Member
    Basic Member
    Posts:109
    Joshua Partogi

    --
    31 May 2013 10:35 AM
    Hi Buatapa,

    Can you please elaborate what you do during this so called Sprint-0 and why do you think it exists?
    Avinash Swami
    New Member
    New Member
    Posts:1
    Avinash Swami

    --
    04 Jun 2013 10:58 AM
    I feel this is mainly derived by PMs for development of integrated components. They try to do the traditional design part as part of sprint 0 specially when they have multiple component integrations, external vendors involved etc
    I have also seen this is the time they try to get the resources on board (hardware and people), trainings, KT etc.
    But as Dominic pointed out its the "project preparation" and can be time boxed for 2 weeks
    You are not authorized to post a reply.


    Feedback