Embed Size (px)
Citation preview
Introduction toUser Story MappingMARK NONEMAN, PROFESSIONAL SCRUM EXPERT
AGILITY SOFTWARE
@MARKNONEMAN
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 1
Getting To Know You!• Agile trainer, coach, consultant◦ Practicing Lean and Agile since 2000
• Worked in a variety of industries:◦ Defense, Telecom, Healthcare, Finance◦ B2B, B2C, SaaS, IT
• Scrum.org certifications:◦ Professional Scrum Developer◦ Professional Scrum Master (I/II)◦ Professional Scrum Product Owner (I/II)◦ Professional Scrum Expert◦ Professional Scrum Trainer◦ Evidence-Based Management
Consultant
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 2
Mark Noneman
Agenda• Product Backlog Foundations
• User Story Mapping• Making Maps Work
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 4
Where Are We Focusing Today?
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 5
Roles
• Product Owner• Development Team• Scrum Master
Artifacts
• Product Backlog• Sprint Backlog• Increment
Events
• Sprint• Sprint Planning• Daily Scrum• Sprint Review• Retrospective
Increment
SprintBacklog
Sprint PlanningMeeting
Retrospective
Sprint Review
Daily Scrum
ProductBacklog
ProductOwner
DevelopmentTeam
ScrumMaster
Product Backlog
The Product Backlog• A hierarchical ordered list of the value-
added features that need to be developed in the product
• One Product Backlog for one product◦ Implemented by one or more teams
• Owned by one Product Owner◦ Who may delegate work to as many others
as necessary while retaining all responsibility
Initiatives
Projects
Capabilities
Activites
Items
Tasks
Definitionof
DONE(DoD)
Sprint Backlog
Use names that match your business needs!
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 6
Writing Product Backlog Items• Often written by the PO + Dev Team together
• Some items start out too big; break them down◦ See reference: richardlawrence.info/splitting-user-stories
Independent
Negotiable
Valuable
Estimated
Small
Testable
INVEST in good Product
Backlog Items…..
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 7
• From Extreme Programming framework (not Scrum)
• Originally had no standard format, just the “3-C” process:◦ Card: craft a title and short description that fits on one index card◦ Conversation: talk with users & developers about it and iterate◦ Confirmation: how will we know we’ve got it? (Acceptance criteria!)
• Standardized format helped people “get it”◦ <Title>: As a <user>, I want <behavior>, so that <business value>.◦ Or just: Title: who?, what?, why?
User Stories
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 8
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8
Release 1Release 2
Presentation / User Interface
Business Logic / Services
Database / Integration
PBI 1
PBI 2
PBI 3
Slices cut across all sub-
systems
Thin, Vertical Slices
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 9
Here’s the Problem…As an office worker, I want to search emails by keyword…
As a scheduler, I want to view appointments by the month…
As an office worker, I want to open unread emails…
As an office worker, I want to delete emails…
As a scheduler, I want to create an appointment using text-only…
As an office worker, I want to move emails from one folder to another…
As an office worker, I want to create and send RTF emails…
As an office worker, I want to create and send HTML emails…
As an office worker, I want to change email format from HTML to text-only…
As a scheduler, I want to view appointments by the week…
…
As a scheduler, I want to create RTF appointments…
As a scheduler, I want to create HTML appointments..
As a scheduler, I want to update the content and location of appointments…
As a scheduler, I want to propose a new time for an appointment…
As a scheduler, I want to invite people to a meeting…
…
As an office worker, I want to create sub-folders within existing folders…
As an office worker, I want to create and send basic text-only emails…
As an office worker I want to create basic contacts for email and calendar meetings …
As a scheduler, I want to view a list of appointments…
As a scheduler, I want to create RTF appointments…
As a scheduler, I want to view a specific appointment’s details…
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 10
LEGENDIn processTo doDone
Agenda• Product Backlog Foundations
• User Story Mapping• Making Maps Work
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 11
User Story* Mapping• Product Backlogs are one-
dimensional◦ This makes it difficult to see the
workflow, relationships, and dependencies
• Story maps help visualize and plan upcoming work◦ They foster collaboration by
providing different perspectives
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 12
* Maps do not necessarily use user story format. Instead the map “tells the story” of how the user uses the product.
Story Mapping• What are all the things that you do to
get ready to go to work?◦ Starting from the moment you wake up
until you arrive there◦ Write one item per sticky note; use verbs!
• Group them into similar kinds of things◦ Label the groups as “activities”
• What things would you do if you only have 15 minutes before you leave for work?◦ Move those higher, other things lower
• Now, what if you only had 5 minutes?July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 13
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 14
Story Mapping
Decompose and create a story map forthe product provided by the instructor.
Your instructor is the Product Ownerand will answer questions on scope.
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 15
Agenda• Product Backlog Foundations
• User Story Mapping• Making Maps Work
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 16
Story Map Next Steps• Continue to refine the minimum features needed in each release for
each user activity◦ Identify & clarify new features◦ Break down large features into small vertical slices◦ Development Team estimates effort◦ Reprioritize individual user stories
• In other words, continuously REFINE your User Story Map
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 17
Using Your Map
• The map IS your Product Backlog!
• Make it visible!• Continuous refinement• Inspect & adapt at Sprint
Review (or equiv)
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 18
• Mike Cohn, Mountain Goat Software (mountaingoatsoftware.com)◦ Recognized expert on user stories and estimation◦ “User Stories Applied”
• “User Story Mapping” created by Jeff Patton◦ Relatively new technique to create visual, 2D Product Backlogs
• “How to Split a User Story” by Richard Lawrence◦ www.richardlawrence.info/splitting-user-stories
User Story References
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 19
It’s Your Product Backlog!• It’s up to you!
• What will you differently when you get back to your offices/teams:◦ Tomorrow?◦ Next week?◦ Next Sprint?
July 2015 COPYRIGHT © 2015 AGILITY SOFTWARE 20
Mark NonemanAgility Software
[email protected]@marknoneman
