Story splitter
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
…umpf, a big chunk.
✣ ✣ ✣
Get a big thing done.
Why split stories?
- Reduce uncertainty
- Early and faster feedback
- Easier time estimation
- Faster value to customer
- Visible work progress—visible flow
- Clearer responsibility
- Earlier start of work/code/test/execute
- Easier distribution across team
- Easy to debug
- Easy to test and validate
Therefore:
Split it into bite-sized chunks that each deliver value.
✣ ✣ ✣
✣ ✣ ✣
Because small is beautiful, there is a strong preference for small items, as they:
- enjoy shorter short cycle times;
- show more progress on the kanban board;
- take less effort to complete;
- are easier to understand;
- are easier to test and accept;
- provide a predicable and continuous flow that facilitates expectation management; and
- make “past results are a guarantee for the future” come true, just like yesterday’s weather.
To be specific, in planguage this looks like:
Small Stories | |
---|---|
Scale | Average number of days per item. |
Meter | Track the number of days per item in a control chart. |
Wish | ≤ 2 days |
Goal | ≤ 3 days |
Must | ≤ 5 days |
Now | 20 days |
Therefore |
|
Sources
- SlideShare » Neil Killick » Effective Story Slicing
- Google Docs » Henrik Kniberg, Alistair Cockburn » Elephant Carpaccio Exercise Facilitation Guide
- Alistair Cockburn » Alistair Cockburn » Elephant Carpaccio exercise
- Pareltaal » Martien van Steenbergen » Verhalenhakker
- InfoQ » Savita Pahuja » Empirical Measurement of Cycle Time by Slicing Heuristic
- xProgramming » Ron Jeffries » Getting Small Stories
- NeilClick.com » Neil Click » My Slicing Heuristic Concept Explained
- xProgramming » Ron Jeffries » Slicing, Estimation, Trimming