Decouple stages

From Pearl Language
Jump to: navigation, search

…you have a proper visual workflow in place.

✣  ✣  ✣

Stages should be independent to reduce coupling, increase cohesion, and promote autonomy.

You aim for maximum cohesion, minimum coupling and disciplined autonomy, yet autonomy and independence also:

    • create opportunities for parallelism; and
    • hamper information flow.

Therefore:

Serialize the steps and set up an agile contract between stages, especially if they involve another party. Impose a blocker count limit that, when exceeded, pulls the andon cord to swarm the issue.

✣  ✣  ✣

Handoffs between steps should take place via well-defined interfaces. This enables to automate one or more of the steps, or to let inexpert staff carry out the step.

The andon cord is similar to the boom buffer.


✣  ✣  ✣

[[so::Serialize the steps and set up an agile agreement between stages.|]]
Facts about "Decouple stages"
Goalsupport very long wait times while keeping short cycle times. +
PearlVisual workflow +, Maximum cohesion, minimum coupling +, Disciplined autonomy +, Agile contract +, Blocker count limit +, Andon cord +, Swarm the issue +, Boom buffer + and Agile agreement +
ThemeAgile + and Lean +
WishStages should be independent to reduce coupling and promote autonomy. +