The Importance of Sprint 0
Once you decide to go somewhere you aren't going to jump into your car and start driving without considering how you're going to get there. Even on a short trip you're going to have a route in the back of your mind before you head off. The same applies to Agile projects - once you have approval to start building something you can't simply jump into Sprint 1 without doing some preliminary planning. Even though Agile generally discourages too much up front planning, some planning is essential. Otherwise you run the risk of getting lost. In this presentation we'll discuss what Sprint 0 is and why it's important.
Outline/structure of the Session
In this presentation we'll cover:
- What is Sprint 0?
- Why do a Sprint 0?
- What do you need to start a Sprint 0?
- What are the key things that need to get done?
- What is the expected outcome (Sprint 1 of course!)
- Who are the key players?
To promote interaction, audience members will be asked to provide their thoughts on the answers to the above questions. I'll enhance the conversation by providing examples from teams that I've recently worked with that have not done a good job of Sprint 0 at the beginning of their projects - and yes, they're lost!
This presentation could easily fit into a 40 or 60 minute time slot.
Attendees will gain a better understanding of what Sprint 0 is and why it's an important part of the Agile approach.
This presentation will be of interest to roles that tend to get involved with starting new projects - Project Managers, Architects, etc.
Attendees should have a basic knowledge of Agile practices and planning processes.