Enquiries: +44 (0)20 7692 4832

Agile Business Change Blog Thoughts on Agile Strategic Business Change and Agile Delivery

12
JUL

Why do agile projects fail?

12 JUL 2012 | Posted in agile development, project failure | Author Stan Wade | 2 Comments

I was in a meeting a few days ago and a customer of mine who is a deep believer in agile development mentioned an article he had on the top 10 reasons agile projects fail. I had probably already read it, but it still sounded interesting so I had a quick search and of course found a number of top ten lists published, so….I read them all.

There was quite a bit of commonality and in general the following issues were highlighted:

  • Poor/Lack of Business leadership
  • Poor scrum master/ team leadership
  • Lack of business engagement
  • Poor decision making process
  • Poor learning culture/ retrospective process
  • Poor communications
  • Lack of transparency
  • Lack of skilled support on site
  • Lack of team focus / Commitment
  • Requirements management and scope creep
  • Poor completion criteria

These are all reasonable statements and I can remember examples of all of these on projects I have been involved in. However what I was rather surprised not to see was anything about poor project initiation and lack of appropriate up front planning. Are we happy to dive in on day one and start coding without any design or preparation? I certainly have found evidence on blogs that some people believe that this is ‘agile purity’ and they don’t like it. So why do it?

I think poor project initiation/initial planning is a significant reason why projects can fail. Failure to identify uncertainty and decide how to manage it is the ‘running into a dark room clutching a pair of scissors’ scenario. I accept there is a risk of getting the amount of up front planning and design ‘right’ is a challenge, but I am pretty sure it’s rarely zero.

Effective project initiation is key to success and cannot be left to a Sprint 0 or a ‘we will do it as we go’ some things are simply too big and dangerous to ignore and hope they will just go away or work out in the wash. 

Comments

Do these apply uniquely to Agile? It seems to me that these are the reasons 90% of projects fail, Agile or non-Agile, in IT or outside IT.,

reply

Another take on this is determining if failing agile projects have been agile. I have met many people who claimed to have been working on agile projects over the last 5 years. On discussion, it transpires that most have been using a few techniques and called their process "agile". (My favourite was the agile project that had one stand-up meeting a week). These projects will fail or not deliver the expected benefits which then in the eyes of unknowing managers leads to failed agile projects.

reply

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

Stan Wade's picture

I'm an Agile mentor with more than a decade's experience of Agile. I mainly work on corporate Agile transformations, but with my varied background, am fairly confident I can handle most roles on software delivery.

WHAT WE'RE SAYING

17
JUN
Would Like, Will Not get?

I recently had a debate with Simon Annicchiarico of Appius regarding the meaning of the W in MoSCoW, and whilst it had its origins in my petty pedantry, there was an important issue to be considered.

11 JUN
Shit Happens
ABOUT US OUR SERVICES SECTORS BLOG CONTACT
How We Work Our Philosophy Management Team Our Clients Case Studies Agile Change Strategy Building Agile Capability Agile Programme Delivery Financial Services Government Media Not for Profit Retail Would Like, Will Not get?... on the nature of governanceShit HappensAgile Development Survey Results