Change Manager: risk, authorization, and coordination
Six lessons, 30 questions, and nine cases on authorization, risk, dependencies, evidence, readiness, urgency, and change improvement.
Objectives and progression
A professional assessment with six modules on mandate, impact analysis, scheduling, traceability, execution decisions, urgency, and improvement. Practice fictional certificate, middleware, rollback-capacity, GitHub and GitLab approval, canary, and temporary-permission cases. Includes primary sources, explanations for every option, and an internal assessment of 27 decisions in 60 minutes. Distinguishes intended control from actual configuration and vendor examples from local processes. Awards no external certification.
Audience: Change managers, APS professionals, service owners, and change decision participants.
Prerequisites: Experience collaborating in technical teams and delivery and support fundamentals; no prior certification required.
300 estimated study minutes
- Clarify decisions and apply a process proportionate to change risk.
- Assess change across the complete service and coordinate window conflicts.
- Connect the decision to the actual version and confirm how approvals work.
- Consolidate operational conditions and criteria to proceed, stop, or recover.
- Coordinate urgent changes without losing authority, state, or follow-up work.
- Confirm the outcome and improve the process with contextual evidence.
Modules
- Mandate, models, and authorization
- Impact, dependencies, and calendar
- Evidence, artifacts, and controls
- Readiness and execution decision
- Urgency, deviations, and recovery
- Closure, metrics, and improvement
Continue learning
References and version
NIST SP 800-128 updated October 2019; DORA five-metric model and change approval guidance; vendor documentation inspected 2026-10-01
- Guide for Security-Focused Configuration Management of Information Systems · 2026-10-01
- SP 800-128 full publication · 2026-10-01
- Streamlining change approval · 2026-10-01
- Safe deployment practices · 2026-10-01
- Canarying releases · 2026-10-01
- Release engineering · 2026-10-01
- The evolving SRE engagement model · 2026-10-01
- DORA software delivery performance metrics · 2026-10-01
- Deployments and environments · 2026-10-01
- Deployment approvals · 2026-10-01
- Disaster recovery strategies · 2026-10-01
- Postmortem culture · 2026-10-01
What you will explore
0 / 6Mandate, models, and authorization
Clarify decisions and apply a process proportionate to change risk.
Impact, dependencies, and calendar
Assess change across the complete service and coordinate window conflicts.
Evidence, artifacts, and controls
Connect the decision to the actual version and confirm how approvals work.
Readiness and execution decision
Consolidate operational conditions and criteria to proceed, stop, or recover.
Urgency, deviations, and recovery
Coordinate urgent changes without losing authority, state, or follow-up work.
Closure, metrics, and improvement
Confirm the outcome and improve the process with contextual evidence.