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:
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.
While I was working with one of my clients a few years a go, I was given a book to read by the CEO. "The Speed of Trust". I read the book with a healthy dose of scepticism having read many management books in the past. But this book resonated with the core principles of Agile for me.
Comments
25 Jul 2012 19:43
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.,
reply31 Jul 2012 21:49
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.
replyPost new comment