November 20, 2026

74% of organisations report negative impact of agile project delivery methods

placeholder

Fiona MacIntyre, Pulsion takes a look at how agile software development is working in practice – the results are interesting.

With a general feeling, and from hearing some rumblings of distrust of agile, we commissioned an independent research report via Vanson Bourne exploring Agile Software Development and the results are enlightening.

Although widely used and still regarded fairly well – there is a feeling that it’s not all it’s cracked up to be, with 74% of those asked stating that they had experienced a negative impact of adopting agile delivery methods. The most common issues being around difficulties in predicting timelines and costs.

There’s no doubt that it’s super trendy to say you have adopted Agile and work with Agile project delivery methods. Certainly in our world of software development, it’s expected this will be a way of working and we wholeheartedly agree it can have huge benefits to your organisation when done right but Agile was never designed to work without structure.

Our research revealed that 61% of Public Sector organisations believe that predicting timelines is more difficult and 50% of mid size companies have seen projects over-run.

Why is this?

One theory is that agile can create small silos of activity and with one person working on one area, the big picture is not always taken into account. i.e. – what impact does that piece of work have on the overall project? It’s all well and good having one part complete if something that will be part of a future build will impact what has just been done.

John McGuire, Owner, Pulsion explains

“One analogy I often use is that of a car that needs an accelerator pedal. Someone could go off and build that with no indication of the full picture that this pedal can’t be so big it takes up the full space. Then picture the scene two weeks later when it’s realised that a brake is also needed. Oh dear – that accelerator pedal is too big and there’s no room for the brake. The result? Rework. The first pedal built will need to be rebuilt smaller to make room for the second requirement. Rework makes it impossible to predict timelines and costs which is what the results of our report have pointed to. Ok – that’s an extreme example, but you get the point. It’s essential that we work hard in the specification phase of the project and we believe that documentation is still important here. If you get the scope detail right, it avoids the need for as much re-work”

Agile can’t work with people working in isolation. 60% said there is low understanding within their organisation about the different agile methodologies available. As with most things it’s essential that every part of the business understands what you are doing and why you are doing it.

Even more alarming is that 51% said Stakeholders/senior managers in their businesses don’t understand agile. This is going to make it a real challenge to work within a business moving to agile and would explain why we found that the morale of development teams has been affected. More than a quarter of companies we spoke to stated there has been a slump in morale within their development teams since adopting agile.

Agile can only work if the full end-result has been fully specced out, outcomes agreed and then broken out into the tasks required to deliver and with related tasks identified. It doesn’t have to be like this. Agile may have its detractors but done right it can be a highly effective tool in project delivery.

We know this will be a divisive topic, with lots of avid supporters of Agile methods, we’d love to receive feedback.