The Importance of Sprint 0

process Talk 40 Mins Intermediate
Lawrence Ludlow
Lawrence Ludlow
Director, Agile CoE
Intelliware Development Inc.

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.

 
0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

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.

Learning Outcome

Attendees will gain a better understanding of what Sprint 0 is and why it's an important part of the Agile approach.

Target Audience

This presentation will be of interest to roles that tend to get involved with starting new projects - Project Managers, Architects, etc.

Prerequisites for Attendees

Attendees should have a basic knowledge of Agile practices and planning processes.

schedule Submitted 5 years ago
Toronto Agile Community 2017

Toronto, Canada

Tue, 7th Nov 2017

email Contact Us
Call for Proposals CLOSED
Ended on Aug 18 '17 11:59 PM EDT

The program will feature time slots of 40, 60 and 90 mins:

  • The 90 minute time slots will be reserved for workshops and will take place in the morning, after the keynote.

  • There will be two 40 minute time slots that will take place concurrently with the 90 minute slot in the morning.

  • The 60 minute slots will take place in the afternoon.

  • The 40 and 60 minute slots will be for Talks, Panels and Experience Reports

Selection Criteria

  1. Fit with target audience - New to Agile, Practitioners, Software Craftsmen and People in Management positions.

  2. Value to participants

  3. Presenter track record (e.g. previous conference experience, YouTube videos of past presentations are encouraged; you can even record yourself giving a lightning talk of your session proposal)

  4. Overall program balance (reduce overlap / duplication of topic/mixture of interactive/non-interactive sessions)

  5. Is a good session. Please refer to the TAC site page: Characteristics of a Good Session

Details play_arrow
Speaker Compensation
flightTravel allowance info_outline
hotelAccommodation covered info_outline
confirmation_numberFree conference pass info_outline
Active Members
help