Use Agile to Fight Failure

The purpose of agile is to create working software and solutions.  I have stated this goal repeatedly.  The iterations, meetings, and emotional labor are all designed to get work completed promptly.  The rapid feedback delivers value in the least amount of time without waste exposing failure.  The real test of an agile team is how it copes with failure.

The world of politics, media, and business loves to celebrate winning and success.  John F. Kennedy remarked that success had many fathers, but failure was considered an orphan.  People with careers on the line will do anything to avoid failure.  In a world of achievement, the stigma of failure is very real.  I suspect this stigma makes it hard for business leaders to experiment and try different approaches to problems.  To do so is to risk failure.

Failure is a clarifying experience. We quickly discover what does not work.  We also understand the conditions we are working to overcome.  Failure also creates an emotional connection to the work.  The chip on the shoulder drives you forward, which says to the world, “I may have failed now, but it will make my future success more powerful.”  I extol the virtues of failure because it makes people and teams better at overcoming adversity.  I have failed a lot in my career, and that wisdom follows me.  It helps me train others to avoid the mistakes I have made in the past.

A team has three reactions to failure.  The first reaction is apathy.  If failure has no repercussions, people will continue their bad habits and personal agendas.  The subsequent response is fear, where people behave in self-preservation mode.  Team members withdraw from each other and look to do just enough work to avoid blame or blame someone else.  Leaders micro-manage because they feel helpless and see the people they lead as unable or unwilling to do the job.  Fear is a palatable emotion, and everyone experiences it on the team.  The final sentiment is determination.  Where the fear once existed, the emotional survivors of the group become determined to overcome their adversity.  Good leaders and coaches get teams to the point of determination quickly.  Those with less skill will have to slog through the earlier steps.

Agile and scrum help along this process, exposing failure and forcing the team to inspect and adapt.  Each retrospective allows the team to find and address the points of failure.  The team reflects on what they need to do and what they need to change.  A woman I respect who teaches children says failure is an acronym for the first attempt at learning.  Based on this premise, failure is a stepping stone to more substantial success.

I have failed more times than I can recall during my career.  Each setback, mistake, and screw-up has made me a better developer, scrum master, and coach.  I like to point out the mistakes I have made in the past so that other people can learn from them.  This display of vulnerability also helps me build credibility with the team.  I strive to be a leader instead of a boss or manager.  So, when you are creating working solutions for customers, you are going to confront failure.  The critical part of the failure experience is how you learn from it and the emotional strength of the team that should develop the ability to overcome it.

Until next time.