PO Conference Website Part 2: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:Agile:WorkshopsCategory:Agile This exercise provides some experience in creating a Story Map for a conference website. ==Timings== Allow 3...") |
m (Mmusij moved page Creating PO Conference Website Part 2 to PO Conference Website Part 2) |
(No difference)
|
Revision as of 04:41, 8 January 2019
This exercise provides some experience in creating a Story Map for a conference website.
Timings
Allow 3.5 hours for this exercise.
Equipment
- Flip chart paper
- A4 paper
- Post-it notes
- Markers
- Coloured dots
- Planning Poker Cards
- Anatomy of a User Story Poster
- Affinity Estimation Poster
- Planning Poker Poster
- Ouija Board Sizing Poster
- Kano Analysis Poster
- MVP Poster
- Buy a Feature Poster
- Story Mapping Poster
Tasks: Understanding The Solution
- Crazy 8s Sketching: set the timer for 8 minutes and as individuals sketch down at least 8 separate ideas for the website on sheets of A4. (Avoid variations of the same idea and instead try to provide 8 unique and new ideas.)
- Put all of the sketches up on the wall and review as a team, Dot Voting your favourite features to form a Feature Heat Map
- Sketch a composite of the website with your favourite features to form a paper prototype
- Draw a story board of the conference website experience on several sheets of paper as a high level user journey that describes the website experience from an attendee’s and speaker’s perspective
- Invite one or two members from other teams to act as customers to provide some feedback on your paper prototype and how it might be used
- Get 2 sheets of flip chart paper and place them on the wall to form the basis for a story map
- Take the user journey sheets of paper and place them across the top of the story map to form the outcome that you would like to provide
- Copy the deliverables from the impact map onto new post-it notes and place them on the Story Map underneath the user journey to form the “spine” of the story map
- Break down the paper prototype as Product Backlog Items with some information from the “Anatomy of a User Story” poster. Place the Product Backlog Items as post-it notes on the story map to form the “ribs” under the corresponding epics to provide a Product Backlog of features to be delivered
- Estimate the Product Backlog Items using one of the following techniques, (the facilitator has the equipment needed):
- Planning Poker
- Affinity Estimation
- Ouija Board Estimation
- Attribute business value to the Product Backlog Items using one of the following techniques, (the facilitator has the equipment needed):
- MVP
- Kano Analysis
- 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 5 Sprints
- For each of the 5 Sprints, write a Sprint Goal on post-it notes paying special attention to using an iterative approach to the website
- Adjust the Product Backlog Items between the Sprint swim lanes to form a release plan over the 5 Sprints
- Call over the facilitator to review and discuss