Change Management

Standard for planned changes to Moodle, integrations, and core IT, including risk, approval, and rollback planning.

Governance AFANDI standard approvals clear reviewed on a regular cycle

Quick overview

This page describes the working standard for Change Management – with a focus on concrete decisions rather than general guidance.

The main focus here is risikoklasse and freigabestufe and testtiefe primarily production change so that teams apply the same standard.

The standard only becomes traceable through linked evidence such as change-request incl. risk assessment and through documented edge cases/exceptions.

Practical focusTopic-specificVerifiable

When this page helps

Typical situations in which this page adds value as a working document, and where another document is more appropriate.

Typical use cases

when for Change Management an organization-wide standard with clear boundaries for change types (standard, normal, emergency) be defined
when decisions about risikoklasse and freigabestufe between teams are currently made differently
when audit or internal review concrete evidence such as change-request incl. risk assessment requests
when Exceptions in the area „changesfreigaben“ more often need to be handled clearly, time-limited, and governed

Less suitable when

when Change Management only about a one-off individual case without need for standardization applies
when a detailed project ticket or a technical step-by-step guide is the better fit

Recommended process

A pragmatic sequence that works in practice, from scope to review.

scope for Change Management tighten the functional and organizational framing; avoid scope gaps (insb. change types (standard, normal, emergency)).
standard decisions define: riskklasse and approvalstufe and Testtiefe primarily Produktivänderung – including the responsible roles.
Exceptions with criteria, deadlines and Re-review modellieren; frequent Edge cases about betroffene systeme and integrationen explicitly abfangen.
Evidence in the standard process verankern (at least change-request incl. risk assessment and testprotokolle / abnahme).
review anhand realer deviations fahren and pitfalls such as „Changes be as „klein“ eingestuft without klare criteria“ in the rule reflect back.

Decision rules

Note: Gemeinsame documentation-Standards stehen in the guideline. This page keeps only fest, was for Change Management functional or technisch entschieden was. Central guideline.

Change Management is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.

Entscheidungsrahmen

For Change Management first define the scope clearly: changestypen (standard, Normal, Emergency).

responsibility

decisions about risikoklasse and freigabestufe and testtiefe primarily production change not implizit lassen, sondern roles and approvals explicitly benennen.

Abweichungsregeln

Allow exceptions only if they do not dilute the standard; especially relevant here are betroffene systeme and integrationen.

review triggers

Verifiable is the rule only, when change-request incl. risk assessment and testprotokolle / abnahme cleanly verlinkt are.

What should be documented

Here only the spezifischen Inhalte about Change Management maintain; general documentation rules remain in the centraln guideline. Central guideline.

The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.

Kontext

terms, scope and boundaries about Change Management specify in concrete terms, including change types (standard, normal, emergency).

Umsetzungsvorgaben

Den standard so record, dass risikoklasse and freigabestufe and rollback-kriterium and abbruchpunkt eindeutig entschieden are.

review path

Name and link evidence directly: Change-Request incl. risk assessment, Testprotokolle / Abnahme, Rollback-Plan and Kommunikationsafterweise.

Offene Punkte / Exceptions

Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with betroffene systeme and integrationen.

Common pitfalls

This section captures real-world pitfalls from Change Management; general guidance belongs in the central guideline. Central guideline.

scope driftet: Changes be as „klein“ eingestuft without klare criteria.
the rule is too abstract: Rollback is described, but not testbar.
evidence is missing: Kommunikation startet only after the Change.
the exception gets out of control: the standard remains abstract without practical context.

Tip: It is better to document three concrete observations from real cases than to keep a long generic list.

Review & maintenance

Check this Page gegen reale processes about Change Management – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.

Were riskklassen consistently vergeben?
Waren Rollback-criteria in the Change eindeutig?
Were Freeze-rules eingehalten?
Is the scope still correct?

Review focus for „Change Management“: changesfreigaben; check especially change types (standard, normal, emergency).

Useful metrics

A few metrics are enough – what matters is that they trigger decisions or improvements.

For „Change Management“ Kennzahlen directly an risikoklasse and freigabestufe and the most frequent Praxisrisiken koppeln.

Change-Erfolgsquote

Anteil Changes without Incident or Rollback

Interval: monthly

Rollback-Rate

Anteil Changes with rollback on Vorzustand

Interval: monthly

approval-Lead-Time

time between vollständigem Antrag and approval

Interval: monthly

Next steps

Add jetzt the concrete Entscheidung about risikoklasse and freigabestufe incl. Verantwortlichen, Datum and Verweis on change-request incl. risk assessment.

On „Change Management“ make especially clear as the next step: which change types (standard, normal, emergency) apply in the standard case and which exceptions are time-limited.