A Comparison Of Agile And ITSM Change Management Mindsets
Let’s Compare Agile And ITSM Thinking
We all know that pushing every change — no matter how big or how small — through a change management process is not only bureaucratic but also introduces delays that most development teams can neither afford nor tolerate. As you begin pursuing improving change management, it is important to understand the differences between traditional IT service management (ITSM) change management processes and a more agile approach. The following table compares both the ITSM and agile mindsets and provides a brief description of the following practice areas: scope, governance, risk analysis, build, testing, deployment, traceability, and guidance.
Change Management Critical Success Factors
When considering how to transition from a more traditional ITSM change management process to an agile change management practice, consider the following critical success factors:
- Automation is a higher priority across build, test, deploy, and traceability factors.
- Advanced machine learning applied to risk assessment can help resources concentrate on higher-risk changes.
- Governance needs to transition from human logging to automated logging.
Culture Needs To Evolve
The biggest and most difficult challenge in transitioning toward an agile practice is the culture. Governance practices for years have required that change management demonstrate a very robust set of controls that are adequately managing the risk to the enterprise. These long-standing practices themselves can introduce risk as more controls are added every time an outage negatively impacts the business. The issue is an overreliance on policies to control risk. The change management process becomes more and more complex, as new gates are added to ensure that risk is held in check. The complexity of the process actually introduces risk, with no one in the organization able to keep all the controls at the forefront of activities.
Not all changes can be successfully managed by agile thinking or ITSM thinking. Your operations need a change management practice that can adapt, supporting innovation and agile development practices while also ensuring that risk is mitigated.
For more on overcoming change management challenges, read my report, Overcome Change Management Paralysis.
Have questions? That’s fantastic. Let’s connect and continue the conversation! Please reach out to me through social media, or you can request a guidance session. Follow my blogs and research at Forrester.com.