1. a process or set of rules to be followed in calculations or other problem-solving operations
Those of you reading this are more than familiar that Agile is all the rage. Executives like to say that their organization is going "Agile". They throw out terms like Scrum and Kanban without truly understanding what they are getting involved in.
In order for Agile to be implemented successfully, I have created the following simple algorithm. Embrace Change + Learn from Mistakes = Agile Implementation Success.
Input 1 = Embrace Change
The primary risk with implementing Agile involves the ability your organization to embrace change. You need to answer the following questions about your organization's culture and your leadership team before you can successfully implement Agile:
How does your organization respond to change?
- When was the last time your organization underwent any major changes?
- Have they been through major layoffs? Have they introduced new leadership?
- How long have they been in business? Have there been major new product introductions?
- Have they been acquired or merged?
How did these changes go? In this case, past performance often dictates future performance. If your company struggles with change, then they will have trouble introducing Agile. Agile introduces change in so many ways:
- Changes in roles, title and responsibilities. Just look at the roles in Scrum, since it is currently the most popular Agile method being implemented. How easy is it for your organization to adopt these roles?
- A Scrum Master? How many managers or project managers do you know who truly understand the concept of servant leadership? How many organizations allow for management positions that do not have direct reports? To truly be successful with Scrum, a Scrum Master role has to be created from scratch, not just assigned to an existing function.
- A Product Owner?? Organizations that have a mature product manager function can transition easily to this, but many organizations manage product related decisions by committee with a team of business analysts. The role of a truly empowered Product Owner is difficult for many companies to swallow.
- A Scrum Team??? A self-organizing team is the foundation of Scrum and of Agile in general. How many organizations actually foster this? How many middle manager's jobs would be eliminated if an organization becomes successful with this? How many under performers would be exposed in this model? This is the most difficult, yet most critical change required.
- Changes to process.
- No analysis or business requirements phase? No Gantt charts? No 12 month project plan? Traditional project management was just formalized at many organization in the last decade. Formal PMOs have been rolled out, massive enterprise tracking tools implemented and teams of project managers hired to create and maintain documentation. Can your organization tolerate getting rid of all the processes you just implemented?
Input 2 = Learn from Mistakes
Only a company or leadership team that has experienced project failures can truly appreciate and support an Agile implementation. These failures may have come in many different ways:
- The project came in too late to meet the market opportunity.
- The budget changes were so excessive that the project was either terminated or deemed a total failure.
- The customer rejected the product because it was "not what they were expecting."
The list goes on and on....The Agile Manifesto was not crafted by grad students developing a thesis. It was developed by people who were clear that the way we were working wasn't working. Many people, like myself, have become Agile evangelists only after suffering through one or more of the above project failures over which we had no control. One of the major downsides with introducing Agile to the "younger" workforce is that they don't truly appreciate how much more fun and enjoyable it is to work on an Agile project. Give them one month of using project time-sheets and hourly tracking in an ERP tool and they will start to see the light.
Output = Agile Implementation Success!
The benefits of Agile are self-evident for those who have lived through traditional project failures and are willing to change. There are hundreds of successful case studies and stories of successful Agile implementation, but implementation failures are becoming more and more common. Becoming "Agile" is not just using the term "Agile", it is a transformation that will effect your entire organization.
Dan Tousignant, PMI-ACP, PMP, PSM, CSPO, CSP
Yes, the key seems to be the organization’s culture and ability to respond to change. It may be because I’ve worked mainly in the government sector but most of my experience has been in organizations suffering from change fatigue – lots of change initiatives kicked-off, not many successfully bedded down. Hence problems with adopting agile. We end up with scrums placed on top of waterfall …