After effects of bad Agile projects.

Written by Praneeth Perna

The article  When Agile Projects Go Bad talks about the bad effects that occur due to implementing agile project management in an erroneous way. He also talks about dangers of implementing Agile techniques as quoted without understanding the principles and spirit of it. He discusses the same with the original authors of the 2001 Agile Manifesto for their advice. The authors of Agile Manifesto give their insight on what could go wrong with the project if Agile is used mechanically and not paying attention to how things are going in the process.

One of the authors of Agile Manifesto Alistair Cockburn says acquisition of skills by people tends to be in 3 stages they are, in the first stage people need to follow a recipe, in second stage that is nice but need more and in the final stage if people ever get there, they don’t know where they are but finally they can borrow and blend.

Alistair Cockburn says in agile projects people won’t succeed if they don’t know where they are going that means they do not succeed if they do not have a project plan, requirements and project scope. Author also mentions that using agile techniques developers use all the tools in the project although they really don’t need them. He also mentions that it is possible people may focus more on processes by neglecting the Agile principles. He also talks about using Agile principles may broke the relationships between the programmers and managers. He also mentions that Agile is not suitable for all types of projects such as Franchises like McDonalds.
Finally Cockburn says Agile works for processes that go through multiple iterations, needs a careful planning and sometimes agile principles may be misinterpreted