Change Management

As technology advances, markets adapt, and businesses grow, enterprise IT infrastructures must be able to adapt to new requirements. However, implementing change requests to a company’s internal systems can be difficult, risky and time-consuming.

In addition, IT changes can directly impact the productivity and engagement of employees who rely on enterprise technology. And whether the change is limited to adding a new office printer or rolling out new technology across the enterprise, the required documentation, approval and implementation is critical. We classify all changes as either standard, emergency or normal and rely on automation wherever possible. This helps to ensure a smooth transition by introducing a set of standardized processes that accompany IT changes from conception to completion.

How does the IT Change Management process work?

1. Change request

Basic information is collected, including notes on potential risks, benefits, and systems likely to be affected. This information is then compiled into an RFC.

2. Modify planning

Now that the RFC has been carefully reviewed, the change must be fully planned. During the planning phase, details such as impact, rollout plans, backout plans, changed roles, and any associated downtime that the change may require should be considered and documented.

3. Change approval

The RFC is sent to the CAB and any other agencies or internal groups that may be affected by the change. The CAB reviews the available information, makes an informed assessment of the risks and benefits, and makes a recommendation to the change manager responsible for final approval.

4. Change implementation

Once the approvals are obtained, the organization can start implementing the change. Implementation involves planning, assigning and delegating the appropriate tasks. By using IT project management, organizations can handle even large-scale changes more effectively and manage a larger number of people and tasks more easily.

5. Modify review

After implementing the change, companies must review and evaluate whether the change was successful and whether there are any unacceptable deviations from the plan. If there are problems, they must be resolved before the change can be completed.

6. Change closure

The change implemented and reviewed is recorded as either successful, failed, or incomplete. Proper closeout documentation helps reduce the risk of duplication and prevents important changes from being lost from the company's view.

Why is it worth it?

Fewer change conflicts

Improved ability to innovate

Fewer failed changes

More accurate classification of changes

Improved automation of innovations

Enabling business results, in accordance with ITIL 4

When simultaneous changes are planned in a harmonious manner, conflicts and overburdened resources are avoided.

This is done without interfering with other operations.

This is possible based on detailed documentation and effective review and evaluation processes.

Creating specific categories for proposed changes allows organizations to address each change in the most efficient manner.

This streamlines processes and frees up teams to focus on other important tasks.

This integrates key DevOps concepts – such as CI/CD, safe-to-fail testing, and shortened feedback loops – into change activities.

Want to know more?

Windows Server 2012 Migration

The technical migration of 1250 servers and the move from Windows Server 2012 were carried out.

The procedure was as follows:

  • Conceptual design, data preparation and planning of the target state
  • Documentation and preparation of the actual state
  • Derivation of measures and recommendations for the migration
  • Planning and coordination of the migration path
  • Management of suppliers and service providers
  • Stakeholder management to ensure support for the project
  • Preparation of a report for the project manager
  • Preparation of documentation and reporting

Migration von Microsoft Server 2012

Die technische Migration von 1250 Servern und der Umzug von Windows Server 2012 wurden durchgeführt.

Dabei wurde wie folgt vorgegangen:

  • Konzeptionierung, Datenaufbereitung und Planung des Zielzustandes
  • Dokumentation und Aufbereitung des Ist-Zustandes
  • Ableitung von Maßnahmen und Empfehlungen für die Migration
  • Planung und Koordination des Migrationspfades
  • Management von Lieferanten und Dienstleistern
  • Stakeholder-Management zur Sicherstellung der Unterstützung des Projekts
  • Erstellung eines Berichtes für den Projektleiter
  • Erstellung Dokumentation und Reporting