These are the slides for my talk at AgileDC.
The abstract for the talk was:
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration and be potentially shippable to production? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Then we will dive into learning techniques for splitting stories in this interactive workshop.
5. www.excella.com
• Placeholder to facilitate communication
• Represents a customer’s request to the
team that creates a product
• Helps prevent misunderstanding
• Best option so far
User Story
10. Starving Student on a Low Budget
to find and purchase food
quickly from my mobile device
I can fill my stomach without
spending a lot of money
As a WHO
WHAT
WHY
What is most important? The Who, the What, or the Why?
I want
So that
Need to understand Why the
Who wants the What.
Important to know Whom this
work is going to benefit.
11. www.excella.com
1. Customer is the person/group requesting
value from team building the product
2. Ideally, Product Owner would write the
user story for the team but in reality that
rarely happens
Notes about the customer
13. www.excella.com
1. Customer is the person/group requesting
value from team building the product
2. Ideally, Product Owner would write the
user story for the team but in reality that
rarely happens
3. Usually, an expert assists the customer
and Product Owner in understanding
what they really want/need
Notes about the customer
14. www.excella.com
• Who is the “Who” in a user story?
• Is the “Who” ever the team doing the
work, e.g., “As a developer, I want to go do
something, so that I can do something
else.”?
• Who typically writes the user story?
Review
17. www.excella.com
Correct
• There is a button in
the upper left
corner of the
screen
Present Tense Indicative Statements
Incorrect
• Put the button in the
upper left corner
• There will be a button
in the upper left
corner
• We need a button in
the upper left corner
23. www.excella.com
Correct
• The drop down
contains each of the
days of the week
• The screen loads in
1.5 seconds or less
95% of the time with
strong 4G signal
Unambiguous
Incorrect
• The drop down
contains Monday,
Tuesday, etc…
• Load time is
sufficiently fast
25. www.excella.com
• Present Tense Indicative Statements, i.e., they are either
TRUE or FALSE
• Generally FALSE before the product has been built
• Must be TRUE for the user story to be accepted
• Include Functional and Non-Functional Requirements
• Complete (All I See Is All There Is)
• Un-ambiguous (no etc., TBDs)
• Include Examples when helpful
Acceptance Criteria
29. AC Splitting
AC
• I can search by genres
• I can search by artist
• I can search by song title
As a <new user persona>
I want to search by genres
So that <new more specific
benefit>
As a <new user persona>
I want to search by artist
So that <new more specific
benefit>
As a <new user persona>
I want to search by song title
So that <new more specific
benefit>
32. www.excella.com
• Form groups of 2 or 3
• Discuss ways to split one or more of the
stories on the worksheet
Group Exercise
33. www.excella.com
• Look for words that could be replaced with
more specific terms
– Nouns, verbs, adjectives, adverbs can all be
generic
– For example
• Vehicle -> Car -> Honda Civic
• Animal -> Dog -> Pug
Generic Words Splitting
Credit: SmallerStories.com
34. www.excella.com
• Form groups of 2 or 3
• Discuss ways to split one or more of the
stories on the worksheet
Group Exercise
35. www.excella.com
• Pretend User Story is done
• “What happens when the functionality is
used?”
• If there is a sequence, then it may be
possible to break into smaller stories
Timeline Analysis Splitting
Credit: SmallerStories.com
36. www.excella.com
• Form groups of 2 or 3
• Discuss ways to split one or more of the
stories on the worksheet
Group Exercise
41. www.excella.com
• Card – Small and could fit on a 3” x 5”
card
• Conversation – It is placeholder for a
conversation to occur in the future. Pointer
to other documents
• Confirmation – Objectives identified
through conversation are placed here.
Three C’s of User Stories
41
43. www.excella.com
• When the Definition of Ready (DoR) is met, the user
story could be developed.
• The Definition of Ready applies to all of a team’s user
stories and is more generic, e.g.:
– Immediately actionable
– Negotiable
– Valuable
– Estimated
– Sized-appropriatey
– Testable
When Can We Start?
46. www.excella.com
• When the Definition of Done (DoD) and
Acceptance Criteria (AC) are both met, the
user story is DONE.
• The DoD applies to all of a team’s user
stories and is more generic
• AC pertain to a specific story
When Are We Finished?
47. www.excella.com
DoD Example
All Code
Checked-in
Unit Tests
Passing
Acceptance
Criteria
Passing
Integration
Test Passing
Performance
Test Passing
With a Product Back Item (PBI)
With a Sprint
With a Release
Security
Audit
Passing
Regression
Test Passing