Embed Size (px)
Citation preview
User Story Mapping
Dr. Serhiy Yevtushenko, 05 Februar 2015
Content
• What is User Story Mapping?
• Basics of User Story Mapping
• How does it relate to other approaches?
• Further Links
What is User Story Mapping?
Approach for:
- Organizing and Prioritizing User Stories
- Checking completeness of planning
- Planning valuable incremental releases
Developed by Jeff Patton
- Has roots in usage-centered design
Used By:
- Attlassian, SAP, Thoughtworks, …
Benefits
- Fixing problems with flat backlog
- Understanding Big Picture
- Seeing features from user perspective
- Building less
- Learning Faster
- Developing iteratively
- May help with finishing on time
What Problems it Strives to Address?
– What is the Big Picture for the Product?
– Can we understand the scope of project before the start?
– What is the minimum functionality that it would sensible for customer to use the product?
– How to group functionality so that every release would deliver useful increment to users?
Anatomy of User Story Map
Types of tasks
Task Type Description
User activity A variety of related tasks performed by a person and directed at a higher-level goal
Major user task What a user does to meet a short-term goal
User story (task-centric) A user story that describes a task a user would like to perform, ideally omitting description of the potential software user interface
How it is done?
• Form groups of 3-5 people
• Brainstorm major user tasks
• Group post-its
• Name groups.
– Use notes of another colour for names
• Arrange groups
– left to right, in order of task completion by user
How it is done? (II)
• Walk through the skeleton
• Add detailed user stories
– Brainstorm user stories for major tasks
– Prioritize them
• Break map into releases
• Slice stories for the first release
Usage Notes
• Provide room with enough space
• Use different post-it note colors for user activities, major tasks and stories
• Write only title of the user story on the post-it note
• Use silent brainstorming during task generation phase
• Discuss the results of brainstorming in groups
• Progress of development could be tracked by attaching sticker of different colors to post-its on map
Where does it Fit in Agile Software Development?
• Best used at Release Planning Level
– For new product development
– For further development of the existing product
• Good fit for usage with Impact Mapping
– User Story Map could be used for detailed planning of the Impact Mapping Outputs
Combining Impact Mapping and User Story Mapping
• Impact Mapping – Business Goals,
– Impacts on Actors and their measurements
– Deliverables achieving impacts
• User Story Mapping – Prioritizing a deliverable
– Optimizing deliverable to achieve user goals
– Understanding of individual user scenarios
– Planning iterative delivery of selected scenarios
Further Links
Book by Jeff Patton „ User Story Mapping: Discover the Whole Story, Build the Right Product“ - http://shop.oreilly.com/product/0636920033851.do
http://www.agileproductdesign.com/ - Jeff Patton web site
https://groups.yahoo.com/neo/groups/agile-usability/ agile-usability Yahoo discussion group
Q & A
Dr. Serhiy Yevtushenko
codecentric AG An der Welle 3 60322 Frankfurt
http://asffm.blogspot.de
