{"id":20059,"date":"2024-02-09T12:52:07","date_gmt":"2024-02-09T12:52:07","guid":{"rendered":"https:\/\/www.topdesk.mom\/en\/?p=20059"},"modified":"2025-05-19T13:01:10","modified_gmt":"2025-05-19T12:01:10","slug":"agile-change-management","status":"publish","type":"post","link":"https:\/\/www.topdesk.mom\/en\/blog\/agile-change-management\/","title":{"rendered":"Agile Change Management Process in Practice"},"content":{"rendered":"

Change Management<\/a> can be a rather rigid and long-winded process. Do you want to make your change implementations more agile? There are different ways to go about this. <\/strong><\/p>\n

This blog will talk about how to implement a single change in an agile way, as well as how to make all your department\u2019s changes more agile.<\/strong><\/p>\n

Agile Service management vs Change management<\/h2>\n

We\u2019re continuing our exploration into Agile Service Management<\/a> \u2013 to find ways you can make your service desk operations more speedy and less rigid. So far, we\u2019ve looked at how ITIL and Agile can work together, drilled into Agile Incident Management and also published a whole e-book on the topic.<\/a><\/p>\n

Most recently, we\u2019ve been exploring change management from an agile perspective. Let\u2019s continue exploring that topic. How does it work in practice?<\/p>\n

Let\u2019s start with how to make the implementation of a single change more agile.<\/p>\n

1. Only describe your goal and preconditions<\/h3>\n

In an ideal world, you don\u2019t fill out a full change request form when you\u2019re first submitting your request. Your description only contains basic information. The most important things you need to include are your goal and preconditions.<\/p>\n

Here\u2019s an example: You often get multiple calls about a coffee machine breaking down or email servers being slow. You\u2019d prefer not to get a bunch of calls about the same problem, so you want your customers to be able to see whether a problem has already been reported.<\/p>\n

Your goal is: showing customers which calls have already been submitted. But you also want to make sure your customers don\u2019t get to see private information of other customers. That would be one of your preconditions.<\/p>\n

Apart from the goal and preconditions, there\u2019s not much you really need to know when you get started with a change.<\/p>\n

2. Check regularly if your change is still meeting the preset goal and preconditions<\/h3>\n

Are you still implementing changes according to the traditional waterfall method? Then there\u2019s always a chance that when you\u2019re done, your solution turns out not to meet the customer\u2019s needs.<\/p>\n

Because the waterfall method assumes that you directly execute the plan you\u2019ve drawn up, without alterations along the way. There\u2019s no room to adjust to new situations. And your situation can change. You may find out new information about what your customer really wants, or there might be new technologies on the market that provide a better solution.<\/p>\n

So, while you\u2019re designing and implementing a change, regularly check the following questions:<\/p>\n