Top Banner
User Story Mapping (USM) Manik Choudhary, PMI-ACP, CSPO, PSM-1 [email protected] Picture Source: Jeff Patton www.AgileProductDesign.com
14
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: User Story Mapping

User Story Mapping (USM)

Manik Choudhary, PMI-ACP, CSPO, PSM-1 [email protected]

Picture Source: Jeff Patton www.AgileProductDesign.com

Page 2: User Story Mapping

Disclaimer

These are my personal opinions on the subject and in no way represent that of my employer.

Page 3: User Story Mapping

How do you combine Design and Development ?

Product Vision Product Backlogs Product Creation

Business Model Framework Business Model Canvas / Lean Canvas

Design Thinking User Story Mapping

Lean / Scrum

Page 4: User Story Mapping

Software Requirements

Use Case

Scenario

User Stories

IEEE 830

http://astheqaworldturns.wordpress.com/category/software-development-life-cycle-sdlc/

Page 5: User Story Mapping

Software Requirements - IEEE 830 Standards

It Shall be possible to Search for the Books

It Shall be possible to Pay for the Books

It Shall be possible to order the Books

It shall be possible to check the status of ordered Books.

http://standards.ieee.org/findstds/standard/830-1998.html

IEEE 830 Standards describe behavior of the software not the behavior or goals of a user

It focus on a checklist of requirements rather than on the users’ Goal

Time consuming to write and Read

Page 6: User Story Mapping

Backlogs

are usually flat You don‘t get the big

picture

Why User Story ?

Source: Jeff Patton www.AgileProductDesign.com

Page 7: User Story Mapping

User Story Mapping

Why User Story Mapping ?

User Story Mapping helps teams to get a common understanding of the requirements from the user's

point of view and it facilitates the backlog creation.

The backlog quality improves & the team wins time

Communication within the team, with other teams and with customers improves

The Three C’s of a User Story

Card

Written description of the Story used for

planning and as a reminder

Conversation

Flesh out the details of the Story

Confirmation

Tests that convey the document details

and can be used to determine when a

story is complete

As a <Persona>, I want to <feature> So

that <Value>

As a Carl I want to

use my credit card to

pay for books so that

it's convenient for

me.

Test with Visa Card

Test with Master Card

Test with Expired Card

Confirmation Conversation

Page 8: User Story Mapping

A Good Story is - INVEST

Independent

Negotiable

Value to users

Estimable

Small

Testable

As Carl I want to

use my credit

card to pay for

books so that it's

convenient for

me.

Picture Source: Jeff Patton

www.AgileProductDesign.com

Page 9: User Story Mapping

Who?

Create the map with the whole team

Enhance and validate the map with customers (End users and business owners) and stakeholders

Picture Source: Jeff Patton www.AgileProductDesign.com

Page 10: User Story Mapping

User Story Mapping – How it looks?

Page 11: User Story Mapping

User Story Map - On Line Grocery Shopping Store

Usage Sequence

Logon

Search for

the Items

Search for

the Items

Place a

Order

Cash On

Delivery

User

Handling Search Order Payment

Credit Card

Vision

Pri

ori

ty

Add to

Basket

BA

CK

BO

NE

W

alk

ing

Sk

ele

ton

fro

m h

igh

to

lo

w

Time

Customer

Owner

As Owner, I want to search

(Via Free Text) for the

Items so that I can quickly

find out the stock of the

items

As Customer, I want to Pay

for the ordered Items using

Cash on Delivery so that I

don't have to enter

payment data on the

internet.

Slicing