Difference between revisions of "Babushka of value"
(Each maturity level includes and transcends all previous levels, just like a babushka doll.) |
(Russian Dolls) |
||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|stage=Sparkle | |||
|theme=Agile, Lean | |theme=Agile, Lean | ||
|context=product development, in the broadest sense. | |context=product development, in the broadest sense. | ||
|wish in a single line=You want a sustainable, ever evolving flow of value creating activities. | |wish in a single line=You want a sustainable, ever evolving flow of value creating activities. | ||
|therefore in a single line=Create and groom an ever evolving minimal set of quality filters in a value stream. | |therefore in a single line=Create and groom an ever evolving minimal set of quality filters in a value stream. | ||
|image=Russian Dolls.jpg | |||
|wish=You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone. | |wish=You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone. | ||
|background=Goals: | |background=Goals: | ||
| Line 13: | Line 15: | ||
*''done'' for upstream equals ''ready'' for downstream | *''done'' for upstream equals ''ready'' for downstream | ||
*downstream defines interface for upstream in collaboration with upstream | *downstream defines interface for upstream in collaboration with upstream | ||
|therefore=Create and groom an ever evolving minimal set of quality filters in a value stream. | |therefore=Create and groom an ever evolving minimal set of quality filters in a value stream. | ||
|new=Each maturity level includes and transcends all previous levels, just like a babushka doll. | |new=Each maturity level includes and transcends all previous levels, just like a babushka doll. | ||
}} | }} | ||
Forces: | Forces: | ||
*{{p|flow to ready}} | *{{p|flow to ready}} | ||
| Line 102: | Line 102: | ||
*For existing applications: Run software update | *For existing applications: Run software update | ||
|} | |} | ||
{{Source}} | {{Source | ||
|author={{mvs}} | |||
|coder={{mvs}} | |||
}} | |||
Revision as of 15:30, 4 November 2011
…product development, in the broadest sense.
✣ ✣ ✣
{{{wish full}}}
Goals:
- maximize flow
- minimize transitions and boundaries—only introduce them when absolutely necessary
- maximum cohesion, minimal coupling (and dependancies)
Design Principles:
- done for upstream equals ready for downstream
- downstream defines interface for upstream in collaboration with upstream
Therefore:
{{{therefore full}}}
✣ ✣ ✣
Each maturity level includes and transcends all previous levels, just like a babushka doll.
✣ ✣ ✣
Forces:
- flow to ready
- sprint to done
- ready for downstream equals done for upstream
Metaphore unto ready to build is the school system: Nursery School -> Elementary School -> Junior High School -> High School.
In the right conditions and within constraints, items develop, unfold, mature in every phase until they are ready for the next. Items ready for the next phase are done in the current.
| In evolutionary stage: | Items are ready when: | Activities to mature until ready: |
|---|---|---|
|
Nursery School |
Any input: wild ideas, brainwaves, anything. |
|
|
Elementary School |
Item matches product goals, as determined by product owner. |
|
|
Junior High School |
Item matches release goals. |
|
|
High School |
Item is aligned with key stakeholders on features, functions and visuals. |
|
|
Poker |
definition of ready, except for planning poker. |
|
|
Build |
See definition of ready. |
|
|
Ship |
ready to ship, a.k.a. definition of done. |
|
|
Deploy |
|