Splitting stories
19 December 2024
Martijn van Steenbergen
Splitting stories
19 December 2024
Martijn van Steenbergen
Please give me feedback :-)
Which parts of the video resonated with you?
Part 1: what makes for a good story?
Starting point
We have specifications for a milestone for which:
Product is happy: it aligns with business goals!
Design is happy: it will provide a great user experience!
Dev is happy: we know how to build this in a reasonable amount of time!
Types of stories
Bugs
Chores
Spikes
User stories
Effects visible to the user
Technical stories
Backend, infra
INVEST
Independent: can be developed and delivered independently of others
Negotiable: details are flexible and open to discussion until picked up
Valuable: delivers clear value to the user
Estimable: can estimate the effort required to complete the story
Small: small enough to be completed within a sprint
Testable: clear acceptance criteria that define when it is considered "done"
— Bill Wake, 2003
The Right Size™️
Common pitfalls of large stories
Too complex to estimate or implement
Dependencies and risks are harder to identify
Delays feedback and delivery
Rule of thumb: about O(10) stories in a sprint (order of magnitude)
What are we doing well? How can we improve?
Part 2: strategies for splitting
Slicing dimensions
Vertical slices
(user stories)
This is the main focus.
Adds value for the user.
Horizontal slices
(tech stories)
Builds foundation for other user stories.
Ways to slice vertically
There are different kinds of things that could be pulled into a separate story:
Simple core + enhancements
Possible ways to interact for the user (UI elements as inspiration)
Business rules
Workflows: can we take a thin slice through the steps? Can we do some steps later?
Data complexity
By user roles
Edge cases
In other words: which requirements do we ignore for now?
Rules of thumb
Main idea: polished after every story (free from bugs)
The user can tell when something is buggy, but they probably can't tell what other features we intend to add
Avoid broken UI (e.g. a button that you can't click)
Separate stories for creating new UI elements (and adding them in Storybook) — a common type of horizontal slice
Build Just In Time: don't make things more generic than necessary
Definition of done (1)
Write story
Write code
Write tests (that pass 😏)
Review
Code is maintainable
Tested / bug-free
Cleanup
Definition of done (2)
Cross-cutting concerns:
Works in relevant browsers
Translations
Accessibility
Security
Performance
Logging/monitoring
Tips & tricks
First version in a text document instead of JIRA
👉🏼 Easier to reorder, split, chat about; less overhead
No more than X open tickets in JIRA at a time (X = maybe 1½ sprint's worth)
👉🏼 Create tickets from text document Just In Time