Why do Agile Adoptions Fail?
Although agilists focus much of their energy on helping their agile projects succeed, it is helpful to periodically stop and consider what causes some agile projects and agile adoptions to fail. Armed with this knowledge, perhaps one can avoid these same pitfalls.
Jean Tabaka lists 11 Ways Agile Adoptions Fail
Agile methodologies have been taking some heat for when they appear to have failed to deliver expected benefits to an organization. In my travels as an agile coach, what I have found to be the case is that agile practices don't fail, rather the variations on agile adoption fail. Here are my top eleven failure modes. See which ones look painfully familiar to you
She lists her top 11, and describes each:
- Ineffective use of the retrospective
- Inability to get everyone in the planning meetings
- Failure to pay attention to the infrastructure required
- Bad ScrumMasters
- Product Owner is Consistently Unavailable or There are Too Many Owners Who Disagree
- Reverting to Form
- Obtaining Only "Checkbook Commitments" from Executive Management
- Teams Lacking Authority and Decision-Making Ability
- Not Having an Onsite Evangelist for Remote Locations
- A Culture that Does Not Support Learning
- Denial is Embraced Instead of the Brutal Truth
Are some (or all of these) familiar from your experiences with agile software development? Would you add to this list?
Tom Hume describes the Why Agile Teams Fail event, summarizing the message as, "if it doesn't work, you aren't doing it right, or your people aren't any cop". QA Strategies itemizes some challenges in agile adoption, from fear of micromanagement to overzealous teams. Kevin Brady thinks agile methods don't account for human psychology:
- People will always put their own interests ahead of the interests of the group.
- People are self-interested
- Commercial production decisions are based on rational expectations.
- Karl Popper's "First law of collective action". You can never get more than 5 people to agree on anything.
Eric D. Brown agrees that it's about the people, goes a different direction: "It isn't the process or methodology used... it is the people involved that will help a project succeed. Of course, processes help, but without good people and an organization that helps those people succeed, any project management methodology will most likely fail."
Re: Excellent list
My first reason
Re: My first reason
Of course, you could say (and would be right), that personal responsibility is the #1 reason for any effective team - Agile or not.
<articlePlug> Read more about it in Personal Agility for Potent Agile Adoption </articlePlug>
Re: Excellent list
I would however add to the list "stick to a clearly wrong technology". It's when you understand that you are using the wrong tool for the job but customer or your manager says "we need to use this one because we bought it". Some PM could sink a whole project because he can't tell the management that some decision must be reconsidered. This, however, is related to "individual responsibility" mentioned by Amr.
Shane Hastie Aug 30, 2014