Embed Size (px)
DESCRIPTION
“Who should write user stories?” “How can I write better user stories?” When should we write user stories?” All questions frequently asked. And all questions entirely missing the point. Just as the *holding* is the most important part of the rental car reservation, the *shared understanding* is the most important part of the user story. Join Kent to learn how user stories help you build shared understanding of the right solution with your team. Along the way, learn some techniques to address common issues that stand in the way of getting everyone telling the same story. Learning Objectives: * Start with value, then identify stories * One way to stop solutioning * Dealing with dependencies (that may not be there) within your backlog * Ways to split user stories into a more manageable size * Mapping your way to acceptance criteria
Citation preview
Anyone Can Write User Stories.It’s the (Shared) Understanding
That’s Important
Kent McDonald
@beyondreqs
All I Really Need to Know, I learned from Seinfeld
Se
infe
ld o
n R
eser
vati
on
s
You see, you know how to *take* the reservation, you just don't know how to *hold* the reservation. And that's really the most important part of the reservation: the holding. Anybody can just take them.
And that’s really the most important part of
the user story: the shared understanding.
Kent’s (Not Me) Simple Idea
“If we get together and talk about the problem we’re solving with software, who’ll use it, and why, then together we can arrive at a solution, and build shared understanding along the way.”- Jeff Patton User Story Mapping
Telling Over
Writing
Topics
Map your way to
acceptance criteria
Use Goals & Objectives to define value
Sometimes, objectives don’t make sense…
Identify Assumptions
Identify stories to validate assumptions & meet objectives
A Flow of Value
Topics
Map your way to
acceptance criteria
Why Bother With the Format?
As Sam the SubmitterI want to submit a session proposalSo that I can share my ideas at the conference
WHO
WHAT
WHY
This way works just as well.
In order to share my ideas at the conference As Sam the SubmitterI want to submit a session proposal.
As Does This One.
Submit a Session Proposal
Who:What: Why:
Why ask Why (and Who & What)
As Sam the SubmitterI want to submit a session proposalSo that I can share my ideas at the conference
Is Sam the Submitter the only role that can do this?
Is this the simplest thing that will allow Sam to share his ideas at the conference?
What information is needed for a session proposal given this reason?
Defining vs Deciding
In order to share my ideas at the conference As Sam the SubmitterI want to…
1) Stakeholders identify “In order to” and “As a”
2) Team proposes several options for “I want”
3) Every one evaluates options and stakeholders decide which approach to implement
50 Quick Ideas to Improve your User Stories by Gojko Adzic & David Evans
Agenda
Map your way to
acceptance criteria
Accounting for Dependencies
UserStory A
UserStory B
UserStory C
Does a Dependency Exist?
Topics
Map your way to
acceptance criteria
Why Split User Stories?
Submit a session proposal
How to Split User Stories?
Topics
Map your way to
acceptance criteria
Topics
Map your way to
acceptance criteria
Testable
Invest
What did you find useful?
@beyondreqs, when I go to work this afternoon, I’m going to try… #baot #valuemgmt
Questions?
If you remember nothing else…1. Writing user stories is not
the important bit. Shared understanding is.
2. Start with value, then identify stories.
3. INVEST is a guide to the types of conversations to have.
Stay in Touch
Kent McDonald
@beyondreqs
www.beyondrequirements.com
Slides available from:
http://www.slideshare.net/kentjmcdonald
