Difference between revisions of "Babushka of value"

From Pearl Language
Jump to navigation Jump to search
(Zeroth version.)
 
m (Fixed format errors.)
Line 28: Line 28:
{|rules="rows"
{|rules="rows"
|-
|-
!align="left" width="20%"|In evolutionary stage:
!align="left" width="15%"|In evolutionary stage:
!align="left"|Items are ready when:
!align="left"|Items are ready when:
!align="left"|Activities to mature until ready:
!align="left"|Activities to mature until ready:
|-
|-
|valign="top" align="right"|
|valign="top" align="right"|
'''Nursery School'''
'''Nursery School''' 
|valign="top"|
|valign="top"|
Any input: wild ideas, brainwaves, anything.
Any input: wild ideas, brainwaves, anything.
Line 40: Line 40:
|-
|-
|valign="top" align="right"|
|valign="top" align="right"|
'''Elementary School'''
'''Elementary School''' 
|valign="top"|
|valign="top"|
Item matches product goals, as determined by {{po}}.
Item matches product goals, as determined by {{po}}.
Line 49: Line 49:
|-
|-
|valign="top" align="right"|
|valign="top" align="right"|
'''Junior High School'''
'''Junior High School''' 
|valign="top"|
|valign="top"|
Item matches release goals.
Item matches release goals.
Line 59: Line 59:
|-
|-
|valign="top" align="right"|
|valign="top" align="right"|
'''High School'''
'''High School''' 
|valign="top"|
|valign="top"|
Item is aligned with key stakeholders on features, functions and visuals.
Item is aligned with key stakeholders on features, functions and visuals.
Line 65: Line 65:
*Identify candidates for Release Planning and Sprint Planning
*Identify candidates for Release Planning and Sprint Planning
|-
|-
|valign="top"|
|valign="top" align="right"|
'''Poker'''
'''Poker''' 
|valign="top"|
|valign="top"|
{{dor}}, except for {{p|planning poker}}.
{{dor}}, except for {{p|planning poker}}.
Line 73: Line 73:
*Converse and converge on significant estimation gaps
*Converse and converge on significant estimation gaps
|-
|-
|valign="top"|
|valign="top" align="right"|
'''Build'''
'''Build''' 
|valign="top"|
|valign="top"|
See {{dor}}.
See {{dor}}.
Line 84: Line 84:
*Technological spikes
*Technological spikes
|-
|-
|valign="top"|
|valign="top" align="right"|
'''Ship'''
'''Ship''' 
|valign="top"|
|valign="top"|
{{p|ready to ship}}, a.k.a. {{dod}}.
{{p|ready to ship}}, a.k.a. {{dod}}.
Line 93: Line 93:
*Publishing.
*Publishing.
|-
|-
|valign="top"|
|valign="top" align="right"|
'''Deploy'''
'''Deploy''' 
|valign="top"|
|valign="top"|
{{p|ready to deploy}}.
{{p|ready to deploy}}.

Revision as of 14:41, 2 November 2011

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

✣  ✣  ✣



✣  ✣  ✣

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.

In evolutionary stage: Items are ready when: Activities to mature until ready:

Nursery School

Any input: wild ideas, brainwaves, anything.

  • Collect and maybe categorize input.

Elementary School

Item matches product goals, as determined by product owner.

  • Analysts decompose.
  • User Experience Expert researches context, characteristics and criteria.
  • Business Analyst identifies business alignment needs.

Junior High School

Item matches release goals.

  • Elaborate item details.
  • Refine acceptance criteria to almost done.
  • Start UE pre-work (wireframes, visual mocks, story boards).
  • Review legal and compliance issues.

High School

Item is aligned with key stakeholders on features, functions and visuals.

  • Identify candidates for Release Planning and Sprint Planning

Poker

definition of ready, except for planning poker.

  • Estimate implementation effort
  • Converse and converge on significant estimation gaps

Build

See definition of ready.

  • Test design
  • Technical design, development and implementation
  • Integration
  • Architectural spikes
  • Technological spikes

Ship

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

  • Hardening.
  • Packaging.
  • Publishing.

Deploy

ready to deploy.

  • For new installs: Purchase application in App Store.
  • For existing applications: Run software update