Difference between revisions of "Babushka of value"
Jump to navigation
Jump to search
(Babushka_of_Value.pdf) |
(Transposed babushka of value table.) |
||
Line 32: | Line 32: | ||
{|rules="rows" | {|rules="rows" | ||
|- | |- | ||
!align="left" | ! | ||
!align="left"| | !align="left"| | ||
!align="left"| | Nursery School | ||
!align="left"| | |||
Elementary School | |||
!align="left"| | |||
Junior High School | |||
!align="left"| | |||
University | |||
!align="left"| | |||
Ready to Poker | |||
!align="left"| | |||
Read to Build | |||
!align="left"| | |||
Ready to Ship | |||
|- | |- | ||
!align="right" valign="top"| | |||
Policy | |||
|valign="top"| | |valign="top"| | ||
Any input: wild ideas, brainwaves, anything. | *Any input: wild ideas, brainwaves, anything. | ||
|valign="top"| | |valign="top"| | ||
* | *Item matches product goals, as determined by {{po}}. | ||
|valign="top"| | |||
*Item matches release goals. | |||
|valign="top"| | |||
*Item is aligned with key stakeholders on features, functions and visuals. | |||
|valign="top"| | |||
*{{dor}}, except for {{p|planning poker}}. | |||
|valign="top"| | |||
*See {{dor}}. | |||
|valign="top"| | |||
{{p|ready to ship}}, a.k.a. {{dod}}. | |||
|- | |- | ||
!align="right" valign="top"| | |||
Activities | |||
|valign="top"| | |valign="top"| | ||
*Collect and maybe categorize input. | |||
|valign="top"| | |valign="top"| | ||
*Analysts decompose. | *Analysts decompose. | ||
*User Experience Expert researches context, characteristics and criteria. | *User Experience Expert researches context, characteristics and criteria. | ||
*Business Analyst identifies business alignment needs. | *Business Analyst identifies business alignment needs. | ||
|valign="top"| | |valign="top"| | ||
*Elaborate item details. | *Elaborate item details. | ||
Line 61: | Line 78: | ||
*Start UE pre-work (wireframes, visual mocks, story boards). | *Start UE pre-work (wireframes, visual mocks, story boards). | ||
*Review legal and compliance issues. | *Review legal and compliance issues. | ||
|valign="top"| | |valign="top"| | ||
*Identify candidates for Release Planning and Sprint Planning. | |||
|valign="top"| | |valign="top"| | ||
*Estimate implementation effort | *Estimate implementation effort. | ||
*Converse and converge on significant estimation gaps | *Converse and converge on significant estimation gaps. | ||
|valign="top"| | |valign="top"| | ||
*Test design. | |||
*Technical design, development and implementation. | |||
*Test design | *Integration. | ||
*Technical design, development and implementation | *Architectural spikes. | ||
*Integration | *Technological spikes. | ||
*Architectural spikes | |||
*Technological spikes | |||
|valign="top"| | |valign="top"| | ||
*Hardening. | *Hardening. | ||
*Packaging. | *Packaging. | ||
*Publishing. | *Publishing. | ||
|} | |} | ||
{{Source | {{Source |
Revision as of 14:15, 14 December 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.
✣ ✣ ✣
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 -> 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.
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 |
|
|
|
|
|
|
|