Enterprise networks and IT environments can be a very unique type of organization to work with. No matter what division is involved, change management can be a stressful thing for an IT environment if not handled correctly. If proper planning is made, then changes can go smoothly! Regardless, there are some nuances you want to keep in mind and problems to be sure to avoid.
Other Teams Within The Change Management Process
When it comes to change management, the team making the change generally has all of their ducks in a row. They have the change thought through, tested, and planned out. When it comes to making that change, they know who is doing what and exactly what needs to happen. Then the curveballs get thrown. How many times have you come across a situation like this:
The network team wants to make a change bringing down the edge internet routers while the server admins are doing a mail server migration to the cloud for a group of users. The loss of an edge connection causes the mailbox upload to stop and the server admins to exceed their allotted downtime window to complete the migration.
This is probably not a scenario that is uncommon to many people working in enterprise IT environments. So many times, certain divisions can become very narrow-minded and have a lack of regard for other teams under the greater scope of the IT team as a whole. Those narrow-minded teams are choosing to only focus on their changes and projects. Breakdowns in communication like this have a tendency to escalate into larger, more difficult issues. The reality of the situation is that the teams involved may not even be part of your organization and may include providers like cloud vendors, for example. All of these teams, both internal and external, need to be included in the communication process when it comes to planning your changes.
Know What You Are Affecting Downstream
It’s no surprise that enterprise IT structures can be very complex topologies with many different technologies in play. When it comes to change management, there are so many devices that rely on each other, that serious thought needs to be given when planning upcoming technical changes whether they are on the network, server, or desktop side of things. Take network changes for instance. Simple additions of routes can fix issues with certain network devices while breaking end to end connectivity for others. Dynamic routing protocols can amplify these minor changes as they are shared between devices. Server environments can have this issue as well. Virtual datacenter changes can affect multiple physical hosts containing a wide range of virtual servers. Again, even minor changes can be amplified to affect a large number of devices and users. The due diligence that going into planning IT changes ensures that you as the admin are fully aware of all devices that will be affected when the changes are made.
Be Aware of your Hybrid Environment
Local IT changes are one thing. You can make your changes and can always have local "console" access if needed in the event of something going wrong. In hybrid IT environments, this may not always be the case. Remotely hosted servers such as web servers or cloud hosted domain controllers need special consideration when it comes to the administration process. On-premises processes, such as restoring from a backup, can be very different when taking place on a device hosted in the cloud. Being aware of the affected devices for a change, their location, and the details of their management is ever more important as hybrid IT environments are becoming so common.
Preparing a Strong Change Management Plan
My personal strategy for change management is made up of four particular steps that I always make sure to follow to ensure a smooth change process.
- Have a documented scope of work.
- Communicate the process to all affected parties ahead of time: on-premises and remote.
- Complete prep work beforehand where possible.
- Always have a backup plan and or a rollback process.
Documented scopes of work ensure that everyone is on the same page and all of the steps that need to be accomplished during the change are laid out ahead of time. This ensures everyone is on the same page and all required tasks get taken care of and not forgotten. Once this plan is developed, you can effectively communicate this process to all affected parties. As long as this is communicated in advance other affected users and teams can send any questions or concerns they may have. With maintenance windows getting smaller and smaller prep work can be very beneficial when it comes to the change management process. This can include scripting changes, downloading updates ahead of time, and even scheduling automated tasks. Focusing on these tasks ahead of time can save you valuable time and effort when the window for your change takes place. Lastly, always have a backup plan. This could be as easy as a simple configuration or data backup or even be a bit more involved like a full rollback process. Either way, make sure that if things go south, you have a process laid out that you can follow. This ensures you are never in a situation where there is an “I don’t know what to do” moment, and that’s what is important.
The change management process does not need to be a difficult thing no matter what size your organization might be. With a little bit of planning and some attention to detail, you can ensure that your maintenance windows are stress free and go off without a hitch!