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!
We’ve all seen them. Projects that are being governed by a Steering Committee that is nowhere near as effective as it could be. Or Project Teams that aren’t made up of the right kind of resources causing a project to slow down to a crawl or even stall out completely. As experts in Change Management, we know Steering Committees and Project Teams who don’t work well together can be a fatal flaw in any change initiative.
Change saturation is quickly becoming one of the biggest challenges in organizations across the globe. Our Change Management Consultants see it everywhere they go. “Sure, we can do that.” “Oh, that initiative will improve sales. Let’s get going on it quickly.” While there certainly isn’t a shortage of good ideas out there the bottom line is almost every organization we know has too many initiatives chasing far too few resources.
Imagine a world in which your organization’s most complex issues are solved by a continuous improvement effort and then the new processes are implemented seamlessly into the organization. Where Lean isn’t just a process improvement approach for a few, but a culture shift for the whole organization. An organization that just doesn’t do “Lean,” but where a Lean mindset permeates through the organization. Sounds perfect, right?
In conversations with potential change management consulting clients about a troubled project, or about the need for a change management methodology in their organization, they will invariably mention past projects that have failed but have not been forgotten. There is the ERP implementation that was quietly withdrawn, or the acquisition that has never been fully integrated. There is the shared services implementation that hasn't delivered the intended value.