Difference between revisions of "Story splitter"

From Pearl Language
Jump to navigation Jump to search
(→‎Sources: += Google Docs » Henrik Kniberg, Alistair Cockburn » Elephant Carpaccio Exercise Facilitation Guide)
m (Alistair Cockburn)
 
(11 intermediate revisions by the same user not shown)
Line 2: Line 2:
|goal=get many bite-szied chunks done done
|goal=get many bite-szied chunks done done
|stage=Sparkle
|stage=Sparkle
|theme=Agile
|theme=Agile, Lean, Scrum, Extreme Programming, Kanban
|context=umpf, a big chunk.
|context=umpf, a big chunk.
|wish=Get a big thing done.
|wish=Get a big thing done.
|so=Split it into bite-sized chunks that each deliver value.
|so=Split it into bite-sized chunks that each deliver value.
|wish full=Get a big thing done.
|wish full=Get a big thing done.
|background====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
See {{p|small is beautiful}}
|therefore full=Split it into bite-sized chunks that each deliver value.
|therefore full=Split it into bite-sized chunks that each deliver value.
}}
}}
Because {{p|small is beautiful}}, there is a strong preference for small items, as they:
*enjoy shorter short cycle times;
*show more progress on the {{p|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 {{p|yesterday’s weather}}.
To be specific, in {{p|planguage}} this looks like:
{|rules="rows"
!align="left" colspan="2"|Small Stories
|-
|align="right"|'''Scale'''  
|Average number of days per item.
|-
|align="right"|'''Meter'''  
|Track the number of days per item in a {{p|control chart}}.
|-
|align="right"|'''Wish'''  
|≤ 2 days
|-
|align="right"|'''Goal'''  
|≤ 3 days
|-
|align="right"|'''Must'''  
|≤ 5 days
|-
|align="right"|'''Now'''  
|20 days
|-
|align="right"|'''Therefore'''  
|
#Split items until:
##the item has exactly one {{p|crystal clear acceptance criterium}} (or scenario) specified in {{p|gherkin}}; and
##each {{p|feature}} consists of ≤ 4 {{p|user stories}}; and
##each {{p|user story}} has ≤ 6 tasks.
#Identify and discuss outliers during or right after the {{p|daily standup}}.
|}
==Sources==
==Sources==
*{{web|url=https://docs.google.com/document/d/1TCuuu-8Mm14oxsOnlk8DqfZAA1cvtYu9WGv67Yj_sSk/pub|site=Google Docs|person=Henrik Kniberg, Alistair Cockburn|title=Elephant Carpaccio Exercise Facilitation Guide}}
 
*{{web|url=http://alistair.cockburn.us/Elephant+Carpaccio+exercise|site=Alistair.Cockburn.us|person=Alistair Cockborn|title=Elephant Carpaccio exercise}}
{{WebSourceListItem
*{{web|url=http://pareltaal.nl/Verhalenhakker|site=Pareltaal|person=Martien van Steenbergen|title=Verhalenhakker|language=Dutch}}
|url=http://www.slideshare.net/neilkillick/effective-story-slicing
|site=SlideShare
|person=Neil Killick
|title=Effective Story Slicing
}}
{{WebSourceListItem
|url=https://docs.google.com/document/d/1TCuuu-8Mm14oxsOnlk8DqfZAA1cvtYu9WGv67Yj_sSk/pub
|site=Google Docs
|person=Henrik Kniberg, Alistair Cockburn
|title=Elephant Carpaccio Exercise Facilitation Guide
}}
{{WebSourceListItem
|url=http://alistair.cockburn.us/Elephant+Carpaccio+exercise
|site=Alistair Cockburn
|person=Alistair Cockburn
|title=Elephant Carpaccio exercise
}}
{{WebSourceListItem
|url=http://pareltaal.nl/Verhalenhakker
|site=Pareltaal
|person=Martien van Steenbergen
|title=Verhalenhakker
}}
{{WebSourceListItem
|url=http://www.infoq.com/news/2014/09/slicing-heuristic
|site=InfoQ
|person=Savita Pahuja
|title=Empirical Measurement of Cycle Time by Slicing Heuristic
}}
{{WebSourceListItem
|url=http://xprogramming.com/articles/getting-small-stories/
|site=xProgramming
|person=Ron Jeffries
|title=Getting Small Stories
}}
{{WebSourceListItem
|url=http://neilkillick.com/2014/07/16/my-slicing-heuristic-concept-explained/
|site=NeilClick.com
|person=Neil Click
|title=My Slicing Heuristic Concept Explained
}}
{{WebSourceListItem
|url=http://ronjeffries.com/articles/015-jul/slicing/
|site=xProgramming
|person=Ron Jeffries
|title=Slicing, Estimation, Trimming
}}
{{tag|story}}

Latest revision as of 17:07, 19 November 2017

…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

See small is beautiful

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  
  1. Split items until:
    1. the item has exactly one crystal clear acceptance criterium (or scenario) specified in gherkin; and
    2. each feature consists of ≤ 4 user stories; and
    3. each user story has ≤ 6 tasks.
  2. Identify and discuss outliers during or right after the daily standup.

Sources

Retrieved from "http://pearllanguage.org/index.php?title=Story_splitter&oldid=2909"