User story mapping
•
2 likes•1,528 views
User Story Mapping is an approach for organizing and prioritizing user stories to plan valuable incremental product releases. It addresses problems with flat backlogs by showing features from the user's perspective and understanding the big picture. The process involves brainstorming major user tasks, grouping them from left to right in order of completion, then adding detailed user stories which are prioritized and broken into releases. Combining Impact Mapping with User Story Mapping allows prioritizing deliverables to achieve user goals through understanding individual scenarios and planning iterative delivery.
Report
Share
User story mapping
- 1. User Story Mapping Dr. Serhiy Yevtushenko, 05 Februar 2015
- 2. Content • What is User Story Mapping? • Basics of User Story Mapping • How does it relate to other approaches? • Further Links
- 3. 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, …
- 4. 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
- 5. 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?
- 6. Anatomy of User Story Map
- 7. 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
- 8. 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
- 9. 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
- 10. 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
- 11. 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
- 12. 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
- 13. 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
- 14. Q & A Dr. Serhiy Yevtushenko codecentric AG An der Welle 3 60322 Frankfurt serhiy.yevtushenko@codecentric.de http://asffm.blogspot.de