Welcome to the The Art of Agile Development website. Think of this as the "special features" DVD for the book, only without the DVD. (If you haven't bought the book yet, that's okay... we won't tell if you don't.) Here, you'll find a cornucopia of bonus material, such as downloadable posters, behind-the-scenes material, and new insights.

For more bonus material, see the table of contents. New entries are posted most Wednesdays.

(If there's nothing else on this page, this chapter has yet to be posted. Try the table of contents instead.)

 Print

The Art of Agile Development: Root-Cause Analysis

26 Mar, 2008

in 99 words

When mistakes occur, blame your process, not people. Root-cause analysis helps. What allowed the mistake to happen? What will prevent them in the future? Assume people will continue to make mistakes and build fault-tolerance into your improvements.

One approach: ask "why" five times. Use it for every problem you encounter, from the trivial to the significant. You can apply some solutions yourself. Some will require team discussion, and others need coordination with the larger organization.

When mistakes become rare, avoid over-applying root-cause analysis. Balance the risk of error against the cost of more process overhead.

as haiku

a slug eats dessert...
making lattice from lettuce,
she thins the surplus

Commentary

In the Privacy of Your Own Thoughts

Inside This Section

  • Root-Cause Analysis
  • How to Find the Root Cause
  • How to Fix the Root Cause
  • When Not to Fix the Root Cause
  • Questions
    • Who should participate in root-cause analysis?
    • When should we conduct root-cause analysis?
    • We know what our problems are. Why do we need to bother with root-cause analysis?
    • How do we avoid blaming individuals?
  • Results
  • Contraindications
  • Alternatives

Loading...

Loading comments...