So, about Small User Stories (it came up again recently...)

We like Stories to be as small as possible, so that it’s easier to understand what we have to do, we have more control and flexibility in planning, and that errors in estimation become unimportant.
When is a Story small enough? For instance when...
- It can be done in about 2 days
- A pair of developers can finish the work (including testing, documentation, deployment, monitoring) in about 2 normal developer days
- There’s about 5-10 stories in a one week sprint
Why do we like small stories?

Small is clearer
Small is easier to define
Small is less likely to be misunderstood
Small is easier to test
Why do we like small stories?

Small means we can do iterative development
Small means variability has limited impact
Small things are easier to complete
Small steps make it easier to change requirements along the way
Why do we like small stories?

Small means we get lots of things done, and that feels nice
Small means less risk we get little or nothing done in the sprint
Small means when we're wrong about the size, it's not a big error
Some useful links for getting to small stories:

Getting Small Stories ( @RonJeffries , https://ronjeffries.com/xprog/articles/getting-small-stories/)
You can follow @wouterla.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.