User Story Mapping: Discover the whole story, build the right product

User Story Mapping: Discover the whole story, build the right product + O’REILLY -Jeff Patton /송지은, 최주은 x 2015 Autumn

About Book

1

The intent of the book |

Story Mapping은 우리가 사용자와 그들의 경험에 집중할 수 있도록 길잡이 역할을 함

그 결과, 원활한 소통이 가능해지며

궁극적으로 더 나은 Product를 제공할 수 있음

이 책은 위와 같은 결과를 나을 수 있는 Story Mapping의 방법을 제공함으로써

더 나은 Product를 제공할 수 있는 환경을 만들고자함

Discover the whole story, build the right product

About Author

Jeff Patton

Product Manager, Agile, Lean, UX, Product Design Evangelist

• connects good product management and strategy, lean user experience and agile delivery

practices together

• has authored numerous articles, essays and, most recently, a book, “User Story Mapping.”

• An independent consultant with a unique teaching and speaking style

(he uses hand-drawings and engaging story telling to share his passion for product design)

Jeff has a long, involved history in product design. He has designed and developed software for the

past 20 years on a wide variety of projects from on-line aircraft parts ordering to electronic medical

records. Jeff has focused on Agile approaches since working on an early Extreme Programming team

in 2000. In particular, he has specialized in the application of user-centered design techniques to

improve Agile requirements, planning, and products. His work include Tomax to Thoughtworks.

Currently, Jeff is an independent consultant, providing training, coaching and consulting services.

He’s also available to lecture and speak at various conferences and events.

2

Summary

“Discover the whole story, build the right product”

3

극대화 최소화

극대화: 모든 팀원들이 스토리에 대한 동일한 그림을 그릴 수 있도록 대화와 의사결정을 많이하는 것이 중요함

최소화: 문제 단위를 최소화함으로써 현실적인 성공 과정과 결과를 얻는 것이 중요함

Table of contents

1. The Big Picture

2. Plan to Build Less

3. Plan to Learn Faster

4. Plan to Finish on Time

5. You Already Know How

6. The Real Story About Stories

7. Telling Better Stories

8. It’s Not All on the Card

9. The Card Is Just the Beginning

10. Bake Stories Like Cake

11. Rock Breaking

12. Rock Breakers

13. Start with Opportunities

14. Using Discovery to Build Shared Understanding

15. Using Discovery for Validated Learning

16. Refine, Define, and Build

17. Stories Are Actually Like Asteroids

18. Learn from Everything You Build

전체 그림 그리기

최소한으로 설계하기

빨리 배울 수 있도록 설계하기

제 시간에 끝낼 수 있도록 설계하기

어떻게 할지는 이미 당신도 알고있음

이야기에 대한 진짜 이야기

이야기를 더 잘 전달하기

모든 것이 카드에만 있는 것은 아니다

카드는 시작일 뿐

케이크를 굽듯 이야기를 굽기

바위깨기

바위 깨는 인간

기회와 함께 시작하기

공유된 이해를 쌓기 위한 발견

의미있는 배움을 위한 발견

정제하고, 정의하고, 실현하기

이야기는 혜성과도 같다

실행하는 모든 것으로부터 배우기

4

Read this first

“Shared Documents aren’t shared understanding"

5

Definition


MVP: Minimum Viable Product

- The minimum viable product is the smallest

product release that successfully achieves

its desired outcomes.

- The minimum viable solution is the smallest

solution release that successfully achieves


Product

6








Definition


Product

Product를 만드는 과정

Process

card, conversation, confirmation

\ work process (3C)

6








Definition


ProductStory

Product에 대한 아이디어와

사용자, 사용자들의 맥락 등

Context

Users

Ideas & Product Principles

Details

…


Process

- idea process (Story Mapping)


\ work process (3C)

6


Process


\ work process (3C)

Definition


Story



Context

Users


Details

…









Product

6

MVP

Minimum Viable Product

Questions to approach MVP

1) Why We Argue So Much About MVP : Minimum viable product is not the crappiest product you could possible release.: The minimum viable product is the smallest product release that successfully achieves its desired outcomes.: The minimum viable solution is the smallest solution release that successfully achieves its desired outcomes.

2) Size Always Matters: A right-sized story from a user’s perspective is one that fulfills a need.: A right-sized story from a development team’s perspective is one that takes just a few days to build and test.: A right-sized story from a business perspective is one that helps a business achieve a business outcome.

3) Questions to approach MVP :Who the customers and users are you believe will use your solution :How they meet their needs todays without your solution :How the world would change for them with your solution :How long your solution might take to build

7








Product

Definition


6

Story



Context

Users


Details

…



\ work process (3C)


Process

Work process

Steps of Work process

1

Start

with Opportunities

2

Discover a

Minimum Viable Solution

3

Dive into

the Details of

Each Story During Delivery

5

Evaluate Each Piece

(by daily)

6

Evaluate with Users

and Customers & Stakeholders

7

Release

and Keep Evaluating

4

Keep Talking

as You Build

8

Work process

9

Steps of Work process

1) Start with Opportunities: Use opportunity discussions to agree the problem is worth solving — to make a go forward or trash decision.

2) Discover a Minimum Viable Solution : * DISCOVER minimum viable solutions : Opportunity -> Problems / Lots of Discussions and Collaboration / Solution / Prototype & Test with Users(Iterate) -> Minimum Viable Solution -> Delivery: Use discovery conversations and exploration to find a small, viable solution.

3) Dive into the Details of Each Story During Delivery: Use deep-dive story workshops to discuss the details, break down stories, and really agree : who? what? why? how? -> deep dive in story workshop -> (1) stories in / (2) Right Sized Stories Out / (3) Trash! OUTPUT MINIMIZER

4) Keep Talking as You Build : Use conversations as you build to fill in details and give feedback on what’s being built.

5) Evaluate Each Piece (by daily): * EVALUATE Pieces as a Team: Product Quality: UX? Functional? Technical? (Stories to improve or change the product) / Plan: Done? Velocity? (Stories with

work remaining) / Process: Working? Not working? Change? 6) Evaluate with Users and Customers & Stakeholders

: * EVALUATE with users & customers: users & customers use software to reach a goal / the team observes learns, and writes stories to improve the solution.: Learn by testing meaningful chunks of working software with customers and users.: Keep your progress and quality visible to stakeholders inside your organization.: * EVALUATE with Business Stakeholders: 1) What we’ve built so far / 2) What we’ve learned (problems, questions, ideas) / 3) What we believe is enough to

release 7) Release and Keep Evaluating

: * EVALUATE After Release: Data + Observation -> Insight -> Opportunities: Use metrics and face time with users to really learn if your target outcomes were met.

Card

MAP IN A NARRATIVE FLOW ACROSS MANY USERS

AND SYSTEMS

THE BACKBONE ORGANIZES THE MAP

MAP IN WHOLE DELIVERABLE RELEASES

Card Mapping Process

1

2

3

10

Conversation Audience

User, Product Owner or Manager, Stakeholder, Developer

11

-Different Perspective

Product Owner or Product Manager

“How will this benefit customers,

users and our organization?”

Customers & Users

“What are the edge-cases

and likely points of failure?”

Business Analyst

What are the behavior

details and business rules?”

User Experience Designer

“Who uses this, and

what are their goals?”

Engineer

“How does the software

look and behave?”

Confirmation

Validated Learning

12

- Review as a Team

- Learn from Users

- Learn from Release to Users








Product


\ work process (3C)

Definition


6


Process

Story



Context

Users


Details

…


idea process (Story Mapping)

Steps of Story Mapping

1

Write out

Your Story

a Step at a Time

2

Organize Your Story

3

Explore A

lternative Stories

4

Distill Your Map

to Make a Backbone

5

Slice Out Tasks

That Help You Reach

a Specific Outcome

That’s It! You’ve Learned All the

Important Concepts

13


14

Steps of Story Mapping

1) Write out Your Story a Step at a TimeTasks Are What We Do: User tasks are the basic building blocks of a story map.My Tasks Are Different Than YoursI’m Just More Detail-Oriented: Use the goal-level concept to help you aggregate small tasks or decompose large tasks.

2)Organize Your Story : Maps are organized left-to-right using a narrative flow: the order in which you’d tell the story.Fill in Missing Details

3) Explore Alternative Stories: Narrative flow ( axis x) / Variations , Alternatives, Details (axis y): Details, alternatives, variations, and exceptions fill in the body of a map.Keep the Flow

4)Distill Your Map to Make a Backbone: Activities aggregate tasks directed at a common goal.: Activities and high-level tasks form the back-bone of a story map.

5) Slice Out Tasks That Help You Reach a Specific Outcome That’s It! You’ve Learned All the Important Concepts: Use slices to identify all the tasks and details relevant to a specific outcome: Desire Outcome / Minimum set of tasks that make the outcome possible


NOW STORY MAP • sometimes called a journey map

LATER STORY MAP • pains: things that don’t work, parts people

hate • questions: why do people do this? what’s

going on when they do? • ideas: thing people could do, or that we could

build that would take away pain, or make the

joys even better • joys or rewards: the fun things, the things

that make it worth doing

It’s Now Map, Not a Later Map

15

…and last 1

“Template Zombies and the Snowplow”

-Template Zombie (The project team allows its work to be driven by templates instead of by the thought process necessary

to deliver products.

-It doesn’t need to be written in a template to be considered a story.

-It’s not a best practice, It’s a learning practice.

NOT LIKE THIS LIKE THIS

16

…and last 2

“Mindful of what you want to learn”

NOT LIKE THIS

LIKE THIS

17

…finally the last

“Great art is never finished, only abandoned.”

NOT LIKE THIS LIKE THIS

19

Jeff Patton’s contact point

19

http://jpattonassociates.com/blog/

http://jpattonassociates.com/blog/

Thank you!