Difference between revisions of "Story splitter"

From Pearl Language
Jump to navigation Jump to search
(→‎Sources: += InfoQ » Savita Pahuja » Empirical Measurement of Cycle Time by Slicing Heuristic)
(+= Small is beautiful quantified in Planguage.)
Line 9: Line 9:
|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==
{{WebSourceListItem
{{WebSourceListItem
Line 27: Line 65:
|person=Martien van Steenbergen
|person=Martien van Steenbergen
|title=Verhalenhakker
|title=Verhalenhakker
|language=Dutch
}}
}}
{{WebSourceListItem
{{WebSourceListItem

Revision as of 07:17, 9 September 2014

…umpf, a big chunk.

✣  ✣  ✣

Get a big thing done.


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=2181"