How to Rob A Bank: An Overview of User Story Mapping presented at IIBA Minneapolis/ St. Paul

Transcription

1 How to Rob A Bank: An Overview of User Story Mapping presented at IIBA Minneapolis/ St. Paul Mike Stuedemann, PMP, PMI-ACP, CSP Certified Scrum Professional & Agile Coach

2 Mike Stuedemann PMP, PMI-ACP, CSP 17+ years Information Technology - traditional SDLC and Scrum/Agile Practicing Agile since 2007 Certified Scrum Professional Active member in the Scrum Alliance and the PMI-MN Agile Practitioner Community Married with 3 Boys - based in Andover, MN 2

3 User Story Mapping Agenda What s a User Story? What s the Problem? What s a User Story Map and how can it help me? How to Rob a Bank A User Story Map Exercise Wrap-Up 3

4 What is a User Story? A User Story is a requirement or feature expressed briefly from the user s perspective Describe who has a particular need or want, what that need or want is and why they need it 4

5 A technique from Extreme Programming Many using Scrum adopt this technique for capturing items on the Product Backlog but Scrum does not prescribe this A note about the format shown at the right What is a User Story? 5

6 What is a User Story? Card Conversation Confirmation Stories are traditionally written on note cards Cards may be annotated with estimates, notes, etc. Details behind the story come out during conversations between stakeholders, product owner and team Acceptance tests confirm that the story was coded correctly 6

7 What s the Issue? 7

8 The First Issue 8

9 The Second Issue 9

10 User s Sequence in Time Story Maps Activities are functional behaviors of the user Activity 1 Activity 2 Activity 3 Activity 4 User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Stories are narrative descriptions of the features needed by the user to perform those activities Story Maps visualize the overall product, and thereby help to convey the Big Picture 10

11 How to Create a Story Map 1. Discuss Activities associated with the Product / Service 2. Sequence the Activities 3. Add Tasks (As Necessary) 4. Brainstorm and discuss User Stories associated with the Activities 5. Shift the User Stories vertically based on their business priority 11

12 Story Map Example Activities Tasks Higher Priority User Stories Lower Priority User Stories Reference: 12

13 The Benefits of a Story Map Provide Story Context Shows Relationship between Stories Make value delivery visible Allows for Ordering of Stories by Business Value Allows the identification of valuable product slice Reference: 13

14 Story Maps Allow us to walk Personas through Features User s Sequence in Time Soccer Mom Millennial Activity 1 Activity 2 Activity 3 Activity 4 User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story Hacker Walk each persona through the user sequence Discover gaps in the user stories & how they support the user activities 14

15 Disclaimer 15

16 Exercise: How to Rob a Bank The Setting: You are a self-organizing team planning to rob a bank Your Challenge: Create a User Story Map describing the necessary activities from the time you arrive at the bank until the time you leave the bank Guidelines: Time box: 20 minutes Remember: Things can always change 16

17 Exercise: How to Rob A Bank A Change in Timing? 17

18 Story-Mapping in the Real World 18

19 A Reminder. Remember: at the end of the day, your job isn t to get the requirements right it s to change the world Jeff Patton 19

20 How to Rob A Bank: An Overview of User Story Mapping Summary The purpose of a User Story is conversation, not a document A flat list of User Stories does not provide context it is easy to lose site of the product being built and the relationship of the Stories to one another User Story Maps are a tool to both facilitate conversation and provide context Please don t rob a bank 20

21 Questions 21

22 22

23 Want to get the Slides? Engage in Witty Banter? Provide Feedback (Accusations, Insults)? Contact Mike 23