Depends if you are referring to organization change management or project change control. In both cases it still applies with adaptive delivery, but context will drive the "how".
If you can clarify which change management you are referring to, I can provide a more fulsome response.
Kiron Saving Changes...
Vijay SuryavanshiProject Manager - Engineering| RECARO Aircraft SeatingPlantation, Fl, United States
Divya,
Change management is a separate domain or knowledge area compared to Agile. These two must not be mixed up.
Agile is used compared to waterfall to reduce product life cycle time and build better productivity with the team.
Change management however has to happen in bigger organizations and has to come from the top leadership. (Top down approach must be used assuming the problem is more complex.). Usually, this happens because of sudden change in regulations in an organization OR the leadership at management level may change the strategy or direction of the company. While implementing change management, be clear with vision, where are you now, where do you want to be (in six months). Awareness of transition phase or allowing for the same is important too. Expect resistance from employees or stakeholders. Get in buy in from functional heads first. Justify your change with a strong reason and support or backing from upper management. As functional heads buy in your ideas, trickle it down to all employees or stakeholders. Implement the change, get the feedback from everyone and see if it is working. There are many different models of change management proposed by consulting companies and few researchers. The McKinsey change framework (7S) is one of them which is well known.. (structure, strategy, system, shared values, skill, style, and staff.) there are others like Kotter's, ADKAR, Kubler Ross and Lewin's change models too. Investigate or research each model to know more about them..
Hope this helps.
...
1 reply by Linda Mullally
Jun 30, 2023 1:35 AM
Linda Mullally
...
Vijay is spot on, on every level - separate yet aligned, change management versus agile. I recently built a new team at my last organization, that supported the rollout of agile practices within our IT team, creating a model to be rolled out organization wide. This was a large project deeply involved in change management, but even doing this project used a hybrid, not fully agile, approach.
Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
Change management is a separate domain or knowledge area compared to Agile. These two must not be mixed up Saving Changes...
Vijay SuryavanshiProject Manager - Engineering| RECARO Aircraft SeatingPlantation, Fl, United States
Yes, that is true. And if you look at the way Agile/Scrum works change management is kind of built in. You involve the customer or project sponsor from in the beginning. So there are no surprises. But this change is pertaining to changes in the project which is controlled by CCB in waterfall method usually.
For changes at organizational level, like I said, there are frameworks or models which you have to look at and choose the one that suits best for your organization or needs. Saving Changes...
Linda MullallyProject Manager, Consultant| Strategic Technical Consultant, Project Manager, Learning FacilitatorMa, United States
Apr 10, 2023 1:05 PM
Replying to Vijay Suryavanshi
...
Divya,
Change management is a separate domain or knowledge area compared to Agile. These two must not be mixed up.
Agile is used compared to waterfall to reduce product life cycle time and build better productivity with the team.
Change management however has to happen in bigger organizations and has to come from the top leadership. (Top down approach must be used assuming the problem is more complex.). Usually, this happens because of sudden change in regulations in an organization OR the leadership at management level may change the strategy or direction of the company. While implementing change management, be clear with vision, where are you now, where do you want to be (in six months). Awareness of transition phase or allowing for the same is important too. Expect resistance from employees or stakeholders. Get in buy in from functional heads first. Justify your change with a strong reason and support or backing from upper management. As functional heads buy in your ideas, trickle it down to all employees or stakeholders. Implement the change, get the feedback from everyone and see if it is working. There are many different models of change management proposed by consulting companies and few researchers. The McKinsey change framework (7S) is one of them which is well known.. (structure, strategy, system, shared values, skill, style, and staff.) there are others like Kotter's, ADKAR, Kubler Ross and Lewin's change models too. Investigate or research each model to know more about them..
Hope this helps.
Vijay is spot on, on every level - separate yet aligned, change management versus agile. I recently built a new team at my last organization, that supported the rollout of agile practices within our IT team, creating a model to be rolled out organization wide. This was a large project deeply involved in change management, but even doing this project used a hybrid, not fully agile, approach. Saving Changes...
