#13 Agile Change Management - Part 1

This is the first of a two-part episode, and covers why change management should be agile.

While answering this question we discuss why 'management' and 'agility' can be seen as complementary components rather than a contradiction in itself.

Some examples we explore in regards to how to make change management more agile are: working in iterations, experimenting with different approaches, testing, keeping requirements open and following the principle 'people over process'.

We also go over potential risks to analyse and mitigate. We consider different aspects such as hard deadlines, a communication plan, stakeholder alignment and expectation management, balancing stability with speed, and the willingness to change.

As usual, at the end of the episode we share some questions for your introspection.

New episodes are out every Wednesday morning. Find out more about isno Tech here: https://isno.tech/