teams

Agile methodologies have taken some heat when they appear to have failed to deliver expected benefits to an organization. In my travels as an agile coach, I have found that agile practices don't fail—rather the variations on agile adoption fail. Here are my top twelve failure modes. See which ones may be painfully familiar to you:

Note: This article was originally published on StickyMinds.com as "11 Ways Agile Adoptions Fail."This updated version includes additional information that explains why some agile adoptions that appear to have failed may never have been truly agile to begin with.

Unfortunately, distrust is common in the relationship between managers and employees. But it doesn’t have to be. Taking the time to keep your communication path “weed free” by finding time for one-on-one communication, being open and honest, and listening to your team members’ input will cultivate an open, honest, and trusting culture within your team.

Whether you're being admonished for having more than ten items in the express lane at the supermarket or you are telling off a tester for missing a bug, at some point we've all been on the giving and on the receiving end of The Lecture. We're all human and fallible. Isn't there a more effective (and mature) way to communicate when a problem arises?

Agile agents of change, listen up. Do you remember the Agile Manifesto? How about the part about valuing people over process? J.B. Rainsberger fears that as Extreme Programming becomes more widespread, teachers, consultants, and mentors are losing sight of one of agile’s most important components—teamwork.