better user stories by matteo cavucci
TRANSCRIPT
BETTER USER STORIES
Bosnia Agile Day - Sarajevo, 15 October 2016
WELCOME!
2
3
4
5
6
7
8
TEAM
9
TEAM
CLIENT
10
TEAM
CLIENT
11
TEAM
CLIENT
12
CUSTOMERS
TEAM
CLIENT
15
CLIENT
16
CLIENT
PROJECT MANAGER
17
CLIENT
PROJECT MANAGER
DESIGNERS
18
CLIENT
PROJECT MANAGER
DESIGNERS
DEVELOPERS
3 PEOPLE
25
LET’S GET TO KNOW EACH OTHER
26
27
MATTEO CAVUCCI
28
ALWAYS LOVED STORIES
READING
ALWAYS LOVED STORIES
READING WRITING
ALWAYS LOVED STORIES
READING CREATINGWRITING
32
EMBRACE CHANGES INSPIRE PEOPLE
33
WHAT ABOUT YOU?
34
A SMALL OVERVIEW
What user stories?
35
A SMALL OVERVIEW
What user stories?
Why user stories are different
36
A SMALL OVERVIEW
What user stories? How can we
make it better
Why user stories are different
WHAT IS AN USER STORY?
37
38KENT BECK
39
NATURAL LANGUAGE NARRATIVES
40
BOOK OF REQUIREMENTS
41
42
43
44
45
46
— JEFF PATTON
Shared documents are not shared understanding.
USER STORIES ARE DIFFERENT
47
48
49
LIKE IT OR NOT, WE HAVE STORYTELLING BRAINS
50
51
STORIES ARE DISCUSSIONS
AN USER STORY DEFINITION
CARD CONVERSATION CONFIRMATION
From “Extreme Programming Installed” Ron Jeffries
53
54
55
INDUSTRIAL
56
DECIDE WHAT TO DO
DOING THE JOB
57
POST INDUSTRIAL
WHAT MAKE PEOPLE MOTIVATED
AUTONOMY MASTERY PURPOSE
59
INDIVIDUAL AND TEAM FREEDOM TO RESPOND MARKET CHANGES
60
COMMANDER’S INTENT
Purpose
Desired state
Initial goal
Continuous planning
61
IT’S HARD TO BREAK OUT OF THE “REQUIREMENT” MINDSET
62
TOO MUCH DEFINITION
63
64
ONE PERSON
65
ARE WE AGREE ON THIS?
66
OHHH
67
OH! OH!
68
I’M GLAD WE ALL AGREE THIS
69
STAKEHOLDERS DON’T KNOW ALL THE ANSWER
?
70
— GOJKO ADZIC
Getting business stakeholders to design solutions wasn’t
the intention of user stories.
HOW CAN WE MAKE IT BETTER?
71
72
THINK ABOUT REQUIREMENTS DIFFERENTLY
73
STOP WRITING, START DISCUSSING
74
Handover
STOP WRITING, START DISCUSSING
75
InvolvementHandover
STOP WRITING, START DISCUSSING
76
Involvement
Good questions
Options
Product ideasMinimise rework
77
78
DON’T WORRY ABOUT STORY FORMATS
79
DON’T WORRY ABOUT STORY FORMATS
Template zombies
80
Tell storiesTemplate zombies
DON’T WORRY ABOUT STORY FORMATS
81
Tell stories
Refer to placeholders
Avoid obvious
User side of things
No feature request
82
83
Posted on Twitter by @sammy_lee12From James Shore’s Agile Fluency class
84
STORIES AS SMALL EXPERIMENTS
85
Prediction
STORIES AS SMALL EXPERIMENTS
86
HypotesisPrediction
STORIES AS SMALL EXPERIMENTS
87
Hypotesis
Small
Right or wrong
Learning
88
89
WATCH OUT FOR GENERIC ROLES
90
Average user
WATCH OUT FOR GENERIC ROLES
91
Actual peopleAverage user
WATCH OUT FOR GENERIC ROLES
92
Provide context
Limit scope creep
Focus
Motivations & impediments
Actual people
93
94
CREATIVITY AND INNOVATION
DISCIPLINED EXECUTION
95
96
CONFERENCE SPONSORS
GOLD
SILVER
BRONZE
MEDIA PARTNERS
99
IF YOU WANT MORE
User Story Mapping Jeff Patton O’Reilly
50 quick ideas to improve your user stories Gojko Adzic & David Evans Lean pub
Made to stick Chip & Dan Heath Random House