rainbow sprint plan smidig 2012 johannes brodwall, chief scientist exilesoft
TRANSCRIPT
Rainbow Sprint Plan
Smidig 2012Johannes Brodwall, Chief scientist
Exilesoft
Make sprint planning fun, fast
and effective
Part I:
The dead sprint
“How is this story related to the
vision?”
Each user story is an island
“We need more details”
No, you need the bigger picture
“Oh, no! It’s not perfect!”
There is not plan to revisit features
Customer gets stressed
Developer gold plates
“What did we just see?”
Demo doesn’t tell a story
Part II:
Sprint goal = Demo
What “done” looks like
The right level of quality
Work towards the goal
Part III:
Rainbow plan
Describe the complete release
Usage flow
1. Something happens in the real world
2. The event is communicated to the system
3. The system does something
4. Someone does something with the system
5. …
6. …
7. …
8. …
9. …
10. Some goal is achieved
Usage flow: frugalflights.com1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
What would you do in Sprint 1?
Usage flow: frugalflights.com1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 1: Walking skeleton1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 2: SMS support1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 3: Complete workflow1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 4: Complete SMS1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 5: Web pages1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 7: Integration1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Sprint 8: Spit-and-polish1. A customer wants cheap vacations
2. The customer signs up for daily or weekly notifications of special flight offers
3. Periodically the System checks which customers should get notifications
4. The System checks for offers that matches the customer’s travel preference by looking up flights with the travel provider system
5. The System notifies customer of any matching offers via SMS• Variation: The System notifies customer of any matching offers via email
6. The customer accepts the offer via SMS1. Variation: The customer accepts the offer on the system website
7. The System books the tickets on behalf of the customer
8. The system confirms the booking by sending an SMS to the customer
9. The customer can at any point see their active offers and accepted offers on the system website
10. The customer enjoys a cheap vacation!
Criteria for choosing the next features• Can be used
• Can get user feedback• Can get technical feedback
Conclusion:
Good sprints comes from good demos
Good demos comes from understanding usage and iterating
