Difference between revisions of "Babushka of value"
Jump to navigation
Jump to search
m (→) |
m (dependencies) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=evolve your product as stacked layers of quality | |||
|stage=Sparkle | |stage=Sparkle | ||
|theme=Agile, Lean | |theme=Agile, Lean, Quality | ||
|context=product development, in the broadest sense. | |context=product development, in the broadest sense. | ||
|wish | |wish=You want a sustainable, ever evolving flow of value creating activities. | ||
| | |so=Create and groom an ever evolving minimal set of quality filters in a value stream. | ||
|image=Russian Dolls.jpg | |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 full=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: | ||
*maximize flow | *maximize flow | ||
*minimize transitions and boundaries—only introduce them when absolutely necessary | *minimize transitions and boundaries—only introduce them when absolutely necessary | ||
*{{p|maximum cohesion, minimal coupling}} (and | *{{p|maximum cohesion, minimal coupling}} (and dependencies) | ||
Design Principles: | Design Principles: | ||
*''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 full=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=In short: | ||
:'''Fix the process, not the people'''. | |||
Each maturity level includes and transcends all previous levels, just like a babushka doll. | |||
}} | }} | ||
[[File:Babushka_of_Value.png|thumb|link=http://pearllanguage.org/images/4/45/Babushka_of_Value.pdf]] '''PDF with example on the right.''' | [[File:Babushka_of_Value.png|thumb|link=http://pearllanguage.org/images/4/45/Babushka_of_Value.pdf]] '''PDF with example on the right.''' | ||
Latest revision as of 14:03, 19 July 2019
…product development, in the broadest sense.
✣ ✣ ✣
You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone.
Goals:
- maximize flow
- minimize transitions and boundaries—only introduce them when absolutely necessary
- maximum cohesion, minimal coupling (and dependencies)
Design Principles:
- done for upstream equals ready for downstream
- 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.
✣ ✣ ✣
In short:
- Fix the process, not the people.
Each maturity level includes and transcends all previous levels, just like a babushka doll.
✣ ✣ ✣
PDF with example on the right.
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 → High School → University.
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.
|
Nursery School |
Elementary School |
Junior High School |
University |
Ready to Poker |
Read to Build |
Ready to Ship | |
|---|---|---|---|---|---|---|---|
|
Policy |
|
|
|
|
|
|
ready to ship, a.k.a. definition of done. |
|
Activities |
|
|
|
|
|
|
|