Difference between revisions of "Babushka of value"

From Pearl Language
Jump to navigation Jump to search
(Each maturity level includes and transcends all previous levels, just like a babushka doll.)
m (dependencies)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Oyster
{{Oyster
|theme=Agile, Lean
|goal=evolve your product as stacked layers of quality
|stage=Sparkle
|theme=Agile, Lean, Quality
|context=product development, in the broadest sense.
|context=product development, in the broadest sense.
|wish in a single line=You want a sustainable, ever evolving flow of value creating activities.
|wish=You want a sustainable, ever evolving flow of value creating activities.
|therefore in a single line=Create and groom an ever evolving minimal set of quality filters in a value stream.
|so=Create and groom an ever evolving minimal set of quality filters in a value stream.
|wish=You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone.
|image=Russian Dolls.jpg
|wish full=You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone.
|background=Goals:
|background=Goals:
*maximize flow
*maximize flow
*minimize transitions and boundaries—only introduce them when absolutely necessary
*minimize transitions and boundaries—only introduce them when absolutely necessary
*{{p|maximum cohesion, minimal coupling}} (and dependancies)
*{{p|maximum cohesion, minimal coupling}} (and dependencies)


Design Principles:
Design Principles:
*''done'' for upstream equals ''ready'' for downstream
*''done'' for upstream equals ''ready'' for downstream
*downstream defines interface for upstream in collaboration with upstream
*downstream defines interface for upstream in collaboration with upstream
|therefore full=Create and groom an ever evolving minimal set of quality filters in a value stream.
|new=In short:
:'''Fix the process, not the people'''.


|therefore=Create and groom an ever evolving minimal set of quality filters in a value stream.
Each maturity level includes and transcends all previous levels, just like a babushka doll.
|new=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.'''


Forces:
Forces:
Line 23: Line 29:
*''ready'' for downstream equals ''done'' for upstream
*''ready'' for downstream equals ''done'' for upstream


Metaphore unto {{p|ready to build}} is the school system: Nursery School -> Elementary School -> Junior High School -> High School.
Metaphore unto {{p|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.
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.


{|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"|
*Any input: wild ideas, brainwaves, anything.
|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"|
|valign="top"|
Any input: wild ideas, brainwaves, anything.
*See {{dor}}.
|valign="top"|
|valign="top"|
*Collect and maybe categorize input.
{{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 58: Line 82:
*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"|
{{dor}}, except for {{p|planning poker}}.
|valign="top"|
*Estimate implementation effort
*Converse and converge on significant estimation gaps
|-
|valign="top" align="right"|
'''Build''' 
|valign="top"|
|valign="top"|
See {{dor}}.
*Identify candidates for Release Planning and Sprint Planning.
|valign="top"|
|valign="top"|
*Test design
*Estimate implementation effort.
*Technical design, development and implementation
*Converse and converge on significant estimation gaps.
*Integration
*Architectural spikes
*Technological spikes
|-
|valign="top" align="right"|
'''Ship''' 
|valign="top"|
|valign="top"|
{{p|ready to ship}}, a.k.a. {{dod}}.
*Test design.
*Technical design, development and implementation.
*Integration.
*Architectural spikes.
*Technological spikes.
|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
|author={{mvs}}
|coder={{mvs}}
}}

Latest revision as of 14:03, 19 July 2019

Russian Dolls.jpg

…product development, in the broadest sense.

✣  ✣  ✣

You want a sustainable, ever evolving flow of value creating activities. Flowing Products from Concept to Cash, a Value Stream Map Backbone.

Goals:

Design Principles:

  • done for upstream equals ready for downstream
  • 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.

✣  ✣  ✣

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.
Retrieved from "http://pearllanguage.org/index.php?title=Babushka_of_value&oldid=3004"