Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX

  • 252 views
Uploaded on

Transform your Requirements Process from Delivery to Discovery with Story Mapping

Transform your Requirements Process from Delivery to Discovery with Story Mapping

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
252
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
7
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Tasks require intentional action on behalf of a tool’s user Tasks have an objective that can be completedTasks decompose into smaller tasksTasks often cluster together into activities of related tasks“Read an email message” is a task, “Managing email” is an activity.
  • Involve the team and stakeholdersStory Maps support the primary intent of user stories, rich discussionShared Discovery
  • The backbone of the application is the list of essential activities the application supportsThe walking skeleton is the software we build that supports the least number of necessary tasks across the full span of user experience
  • Reading the activities across the top of the system helps us understand end-to-end use of the system. (Talk through just these when talking with people with short attention spans.)

Transcript

  • 1. STORY MAPPING Product Camp Austin 11
  • 2. User Story Mapping is an an approach to Organizing and Prioritizing user storiesTechnique by Jeff Patton
  • 3. Challenges with One dimensional backlogs • Do you understand the workflow? • Are you able to see the relationship of larger stories to child stories? • How do you validate that your backlog is complete? • What context do you use as a context for prioritization?
  • 4. We want to Shift the Process from a Requirements Delivery Process… False Assumptions: 1. The customer knows what he wants 2. The developers know how to build it 3. Nothing will change along the way
  • 5. …To a Requirements Discovery Process Reality: 1. The customer discovers what he wants 2. The developers discover how to build it 3. Many things change along the way
  • 6. The Lean Startup by Eric Ries
  • 7. What were all the things you did to get ready to be here today? Starting from the moment you woke up until you arrived here Write one item per Post-it note
  • 8. In a small group (3 to 5 people) merge these post-its into a single model Arrange them left to right in an order that makes sense to the group Eliminate duplicates Cluster items that seem similar and create labels for the clusters if items seem to go together
  • 9. User tasks are decomposed into smaller tasks and organized into activities
  • 10. User tasks make ideal user stories
  • 11. User Story Mapping is Collaborative & Fosters Co- Ownership
  • 12. User Story Maps help us see things from a user’s perspective
  • 13. With User Story Mapping you can test for Gaps by Walking the Map
  • 14. The user story map contains two important anatomical features The backbone The walking skeleton
  • 15. Reading the activities across the top of the system helps us understand end-to-end use of the system.
  • 16. User Story Mapping helps you Prioritize with Context
  • 17. User Story Maps help us plan releases in complete and
  • 18. How do you think you could benefit from User Story Mapping?