Where using Agile can go wrong

Agile can be a useful way to work when a project needs to learn and adapt.

The problem starts when the label decides the approach before the team has considered uncertainty and the cost of change.

A project where the label came first

I once inherited a large IT infrastructure project. The project had been told to use a predefined Agile format.

When I reviewed the work, I found that it was likely to cost four times the original estimate. The cost of later change was high. We also had enough certainty to do more planning before the major investment decision. That work would have given decision-makers a clearer view of the investment required.

What this means for your project

This is not a reason to reject Agile. It is a reason to let the situation shape the approach. When uncertainty is high and change is affordable, shorter learning loops can help. When certainty is higher and late change is expensive, more planning before commitment may be the better choice.

Further reading

• Context: Read the Agile Manifesto
• What: Watch: Adapt to uncertainty
• How: Use Simple Rule 07: Be Ready to Adapt