Difference between revisions of "Babushka of value"

From Pearl Language
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" width="15%"|In evolutionary stage:
!
!align="left"|Items are ready when:
!align="left"|
!align="left"|Activities to mature until ready:
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
|-
|-
|valign="top" align="right"|
!align="right" valign="top"|
'''Nursery School''' 
Policy
|valign="top"|
|valign="top"|
Any input: wild ideas, brainwaves, anything.
*Any input: wild ideas, brainwaves, anything.
|valign="top"|
|valign="top"|
*Collect and maybe categorize input.
*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}}.
|-
|-
|valign="top" align="right"|
!align="right" valign="top"|
'''Elementary School''' 
Activities
|valign="top"|
|valign="top"|
Item matches product goals, as determined by {{po}}.
*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" align="right"|
'''Junior High School''' 
|valign="top"|
Item matches release goals.
|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" align="right"|
'''High School''' 
|valign="top"|
Item is aligned with key stakeholders on features, functions and visuals.
|valign="top"|
*Identify candidates for Release Planning and Sprint Planning
|-
|valign="top" align="right"|
'''Poker''' 
|valign="top"|
|valign="top"|
{{dor}}, except for {{p|planning poker}}.
*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" align="right"|
'''Build''' 
|valign="top"|
|valign="top"|
See {{dor}}.
*Test design.
|valign="top"|
*Technical design, development and implementation.
*Test design
*Integration.
*Technical design, development and implementation
*Architectural spikes.
*Integration
*Technological spikes.
*Architectural spikes
*Technological spikes
|-
|valign="top" align="right"|
'''Ship''' 
|valign="top"|
{{p|ready to ship}}, a.k.a. {{dod}}.
|valign="top"|
|valign="top"|
*Hardening.
*Hardening.
*Packaging.
*Packaging.
*Publishing.
*Publishing.
|-
|valign="top" align="right"|
'''Deploy''' 
|valign="top"|
{{p|ready to deploy}}.
|valign="top"|
*For new installs: Purchase application in App Store.
*For existing applications: Run software update
|}
|}
{{Source
{{Source

Revision as of 14:15, 14 December 2011

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}}}

✣  ✣  ✣

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 -> 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

  • 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.