Babushka of value
…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}}}
✣ ✣ ✣
✣ ✣ ✣
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 |
|