Wedding Planner: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:Agile:WorkshopsCategory:Agile This workshop provides some experience in creating a Product Backlog in the form of a Story Map, estimating [...") |
(→Tasks) |
||
(One intermediate revision by the same user not shown) | |||
Line 43: | Line 43: | ||
## [[Ouija Board Estimation]] | ## [[Ouija Board Estimation]] | ||
# Attribute business value to the User Stories using one of the following techniques: | # Attribute business value to the User Stories using one of the following techniques: | ||
## | ## [[Minimum Viable Product]] | ||
## Kano Analysis | ## [[Kano Analysis]] | ||
## Buy a Feature | ## [[Buy a Feature]] | ||
# Add post it notes down one side of the Story Map indicating [[Sprints]] 1-5 to form swim lanes for each of the Sprints | # Add post it notes down one side of the Story Map indicating [[Sprints]] 1-5 to form swim lanes for each of the Sprints | ||
# Adjust the User Stories between the Sprint swim lanes to form a Release Plan over the 5 Sprints | # Adjust the User Stories between the Sprint swim lanes to form a Release Plan over the 5 Sprints |
Latest revision as of 05:34, 8 January 2019
This workshop provides some experience in creating a Product Backlog in the form of a Story Map, estimating Product Backlog Items, attributing business value to items, and crafting a release plan for 5 Sprints.
Learning Objectives
- To be able to create new Product Backlog Items and form a meaningful Product Backlog in the form of a story map
- To order the items in a meaningful way
- To be able to estimate items
- To form a basic release plan
Timings
Allow for 60 minutes for table groups to successfully complete their tasks
Materials
- Each team should have a printed copies of:
- Post-it notes
- Marker pens
- Planning Poker cards
- Poker Chips
- Sticky dots
- Sticky stars
- Flip chart paper
- A4 paper
Workshop Flow
Scenario
The scenario is that your team is working for a wedding planning agency and your task is to provide the best possible wedding within 5 Sprints.
Tasks
- Review the “Story Mapping” poster and arrange the epics and User Stories into a Story Map
- Estimate the User Stories using one of the following techniques:
- Attribute business value to the User Stories using one of the following techniques:
- Add post it notes down one side of the Story Map indicating Sprints 1-5 to form swim lanes for each of the Sprints
- Adjust the User Stories between the Sprint swim lanes to form a Release Plan over the 5 Sprints
- Call over the facilitator to review and discuss
See Also
References
- http://www.mountaingoatsoftware.com/agile/planning-poker, accessed 2014
- http://en.wikipedia.org/wiki/Kano_model, accessed 2014
- User Story Mapping Quick Reference Guide, 2014