PO Conference Website Part 2: Difference between revisions

From AgileMe
Jump to navigation Jump to search
No edit summary
Line 14: Line 14:
* Planning Poker Cards
* Planning Poker Cards
* [[Media:User_Story_Anatomy_Poster.pdf|Anatomy of a User Story Poster]]
* [[Media:User_Story_Anatomy_Poster.pdf|Anatomy of a User Story Poster]]
* [[Media:Affinity_Estimation_Poster.pdf|Affinity Estimation Poster]]
* [[Media:Planning_Poker_Poster.pdf|Planning Poker Poster]]
* [[Media:Ouija_Board_Sizing_Poster.pdf|Ouija Board Sizing Poster]]
* [[Media:Kano_Analysis_Poster.pdf|Kano Analysis Poster]]
* [[Media:MVP_Poster.pdf|MVP Poster]]
* [[Media:Buy_A_Feature_Poster.pdf|Buy a Feature Poster]]
* [[Media:Story_Mapping_Poster.pdf|Story Mapping Poster]]
* [[Media:Story_Mapping_Poster.pdf|Story Mapping Poster]]


Line 33: Line 27:
# Break down the paper prototype as [[User Stories]] 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
# Break down the paper prototype as [[User Stories]] 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 User Stories using one of the following techniques, (the facilitator has the equipment needed):
# Estimate the User Stories using one of the following techniques, (the facilitator has the equipment needed):
## [[Planning Poker]]
## [[Media:Affinity_Estimation_Poster.pdf|Affinity Estimation]]
## [[Affinity Estimation]]
## [[Media:Planning_Poker_Poster.pdf|Planning Poker]]
## [[Ouija Board Estimation]]
## [[Media:Ouija_Board_Sizing_Poster.pdf|Ouija Board Sizing]]
# Attribute business value to the user stories using one of the following techniques, (the facilitator has the equipment needed):
# Attribute business value to the user stories using one of the following techniques, (the facilitator has the equipment needed):
## [[Minimum Viable Product]]
## [[Media:Kano_Analysis_Poster.pdf|Kano Analysis]]
## [[Kano Analysis]]
## [[Media:MVP_Poster.pdf|MVP]]
## [[Buy a Feature]]
## [[Media:Buy_A_Feature_Poster.pdf|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]] or iterations
# 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]] or iterations
# 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
# 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

Revision as of 22:50, 27 February 2019


This exercise provides some experience in creating a Story Map for a conference website.

Timings

Allow 3.5 hours for this exercise.

Equipment

Tasks: Understanding The Solution

  1. 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.)
  2. 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
  3. Sketch a composite of the website with your favourite features to form a paper prototype
  4. 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
  5. 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
  6. Get 2 sheets of flip chart paper and place them on the wall to form the basis for a Story Map
  7. 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
  8. 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
  9. Break down the paper prototype as User Stories 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
  10. Estimate the User Stories using one of the following techniques, (the facilitator has the equipment needed):
    1. Affinity Estimation
    2. Planning Poker
    3. Ouija Board Sizing
  11. Attribute business value to the user stories using one of the following techniques, (the facilitator has the equipment needed):
    1. Kano Analysis
    2. MVP
    3. Buy a Feature
  12. 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 or iterations
  13. 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
  14. Adjust the User Stories between the Sprint swim lanes to form a Release Plan over the 5 Sprints
  15. Call over the facilitator to review and discuss

See Also

References

Retrieved from "https://agileme.wiki/wiki/index.php?title=PO_Conference_Website_Part_2&oldid=1140"