Decouple stages

From Pearl Language
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

…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.|]]