Difference between revisions of "Babushka of value"

From Pearl Language
Jump to navigation Jump to search
m (→)
(Fix the process, not the people)
Line 16: Line 16:
*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=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.'''

Revision as of 15:27, 27 January 2012

Russian Dolls.jpg

…product development, in the broadest sense.

✣  ✣  ✣

{{{wish full}}}

Goals:

Design Principles:

  • done for upstream equals ready for downstream
  • downstream defines interface for upstream in collaboration with upstream

Therefore:

{{{therefore full}}}

✣  ✣  ✣

In short:

Fix the process, not the people.

Each maturity level includes and transcends all previous levels, just like a babushka doll.


✣  ✣  ✣

Babushka of Value.png

PDF with example on the right.

Forces:

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

  • Any input: wild ideas, brainwaves, anything.
  • Item matches release goals.
  • Item is aligned with key stakeholders on features, functions and visuals.

ready to ship, a.k.a. definition of done.

Activities

  • Collect and maybe categorize input.
  • Analysts decompose.
  • User Experience Expert researches context, characteristics and criteria.
  • Business Analyst identifies business alignment needs.
  • Elaborate item details.
  • Refine acceptance criteria to almost done.
  • Start UE pre-work (wireframes, visual mocks, story boards).
  • Review legal and compliance issues.
  • Identify candidates for Release Planning and Sprint Planning.
  • Estimate implementation effort.
  • Converse and converge on significant estimation gaps.
  • Test design.
  • Technical design, development and implementation.
  • Integration.
  • Architectural spikes.
  • Technological spikes.
  • Hardening.
  • Packaging.
  • Publishing.