On a recent new technology implementation for a major, global corporation our consultants quickly realized the new system was actually one of 60 initiatives that were being launched over an 18-month period. Each individual project had its own project team and although there were interdependencies between the initiatives, the project teams were completely unaware of what the others were doing.
We’ve all heard the statistic 70% of all organizational change projects fail. This figure was first reported by Hammer and Champy in 1993 and, unfortunately, recent research confirms the staggering statistic hasn’t changed by much. The ugly truth of the matter is today’s organizations are still plagued by projects that are sub-optimized, if not facing outright failure. “Spotty” implementations are all too common with success in one area but not in all areas impacted by the change.
Operational Excellence programs like Lean Six Sigma have been around for many years and have proven themselves time and time again to be invaluable in identifying areas where business process improvement is necessary. Lean Six Sigma, in particular, focuses on improving performance by removing waste. The five steps in the Lean Six Sigma process are designed to optimize and stabilize business process and design and are abbreviated by the initials DMAIC:
The business value in using a disciplined project management protocol, such as Agile or Waterfall, is undeniable. Project management ensures projects are completed on time, on budget and to scope. And with the amount of investments being made on large, complex organizational change at an all-time high, these metrics are critical. But, what about using a change management process? Is there a value there as well?
You may be surprised to hear us say that being “change adept” requires multiple capabilities, including, but not limited to, a systematic change management methodology like AIM. It’s true. Change management is just one piece of the puzzle!
As organizations attempt to “be Agile” in IT, the PMO, and the business, they’re discovering that becoming an “Agile Organization” is not that simple. There are lots of questions on what actually needs to happen to become Agile, and how to implement what Agile produces.
Last week, Don Harrison, developer of the AIM Change Management Methodology, led a webinar on Implementing Agile: Integrating Change Management for Sustained Adoption. If you don’t already know AIM, you’ll find that it not only complements Agile, it is Agile, and was way ahead of its time! In the session, Don provided practical, realistic guidance on what it takes to become an Agile organization, and what risks you need to be prepared for.
Editor's Note: This article was originally published in July 2017 and has quickly become one of our most popular blogs to date. Because the topic is so timely we have chosen to republish it as this week's blog!
As change management consultants, we’re often asked how Agile and change management fit together. There are a lot of questions about how adding change management to an Agile project management cycle works; there are concerns expressed about whether change management will slow things down, and get in the way of the speed and innovation derived from Agile.
Watch This Quick Video Recap:
Whether your organization uses Agile or a more traditional Waterfall approach to project management there is no doubt the end goal is the same. Getting to value realization for every business initiative is, of course, the name of the game. But, while project management protocols focus on delivering projects on time, on budget and to scope, as change management professionals, we know that is not going to be enough. In order to get to full value realization there is more that needs to be done!