You want Scrum but don’t know how to start – that’s where Scrum Sprint Zero comes in. This blog post on Scrum Methodology explains how creating a sprint to help prepare for the first sprint might be the best way to get your team ready for the new, fast-paced process. As the post explains, having a Sprint Zero might help remove some of the more catastrophic issues that come up later: Since spending too much time on gathering requirements can lead to analysis paralysis, this sprint should be as short as possible — only as long as it takes to accomplish a few preparatory goals. Others, however, argue that sprint zero should be the same length as a regular sprint to help teams adjust to a regular work cadence. With that in mind, it’s not surprising that those who argue that sprint zero should be the same length as any other sprint also assert that it could just as easily be called sprint one. According to these Scrum professionals, the basic goals of sprint zero — design, infrastructure, process improvement, implementation, test, and validation — are the goals of every sprint. The Sprint Zero can’t just be a planning session, though – there should be a tangible outcome to the sprint to help kick start the effort and help the team begin to understand how the work is going to progress. This is why the post suggests adding items to the backlog and writing some code, even if that code is tiny.