Difference between revisions of "Sandbox"

From Pearl Language
Jump to navigation Jump to search
(Labes)
Line 15: Line 15:
*Lean: {{#ask: [[Theme::Lean]]}}
*Lean: {{#ask: [[Theme::Lean]]}}
*Pearl: {{#ask: [[is a pearl::+]]}}
*Pearl: {{#ask: [[is a pearl::+]]}}
*deals with “competing backlogs”;
*can be effectively carried out by merging the backlogs of different product offerings into a single backlog, and then perform backlog management on that single backlog ({{p|one backlog to rule them all}});<ref name="larman vodde scaling practices" Craig Larman and Bas Vodde, ''Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum''. Boston, MA, USA. Addison-Wesley, 2010.</ref>
*uses epic-scale initiatives to express the portfolio vision in practice to guide forthcoming product releases;
*delivers {{p|minimal marketable feature}}s in a steady flow;
<references/>

Revision as of 11:44, 7 June 2012

We just successfully installed the boom buffer. Everyone, including the product owner is very happy, for now the development team can work focused and is not disturbed by external interrupts anymore.

Smart Input Forms Test

foo

elegant checklist

Generated List of all Pearls

Accelerator list
Agile architect
Agile team dōjō
Ambiguity test
Ask for the moon
Babushka of value
Beauty of constraints
Belief statement
Blocker waiting room
Consent
Cruise missile
Customer segment pivot
Daily scrum of scrums
Daily standup
Decouple stages
Definition of done
Don’t just do something, stand there!
Five whys
Focus on focus off
Foreign glimpses
Goldilocks sizer
Habit of changing habits
Improvement board
Innovation accounting
Just say no
Ka-ching a day makes product owner hurray
Kanban
Knowledge injection
Lazy finish
Learning milestone
Minimal viable product
Obeya
One service deserves another
One team
Open space
Pair working
Physical information radiators
Pivot
Product backlog
Product owner
Product portfolio
Product review meeting
Product vision
Product vision board
Ready to build
Reciprocal altruism
Refactor code
Relative estimation
Release burndown chart
Ritual dissent and assent... further results

  • deals with “competing backlogs”;
  • can be effectively carried out by merging the backlogs of different product offerings into a single backlog, and then perform backlog management on that single backlog (one backlog to rule them all);<ref name="larman vodde scaling practices" Craig Larman and Bas Vodde, Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum. Boston, MA, USA. Addison-Wesley, 2010.</ref>
  • uses epic-scale initiatives to express the portfolio vision in practice to guide forthcoming product releases;
  • delivers minimal marketable features in a steady flow;