Change management: production decisions

Objectives and progression

Five modules follow a change from request to subsequent review. The path connects accountability, scheduling, artifact identity, data recovery, and service signals. Questions and cases use fictional financial applications with sufficient information to compare options. This is an independent technical competency assessment, not full ITIL preparation or a BNP Paribas internal policy. It includes no remote command execution or labs.

Audience: APS teams, L2/L3 support, DevOps, and technical managers participating in changes.

Prerequisites: Basic application, infrastructure, and incident knowledge. Examples include the necessary assumptions.

145 estimated study minutes

• Describe change risk, scope, and authority.
• Build a sequence with dependencies and recovery time.
• Relate artifacts, configuration, and recoverable state.
• Decide from evidence and close with validation and concrete actions.

Modules

1. Describe the change and identify authority
2. Build a window that allows decisions
3. Connect the approved artifact to recoverable state
4. Execute in stages and limit impact
5. Validate the outcome and improve the next change

Continue learning

Technical assessments

• Technical Project Manager
• Production Support L3
• Middleware
• Release Management

References and version

DR Change Management 2026.1; independent technical curriculum

• Guide for Security-Focused Configuration Management of Information Systems · 2026-09-29
• Release engineering · 2026-09-29
• Canarying releases · 2026-09-29
• Implementing SLOs · 2026-09-29
• Being on-call · 2026-09-29
• Managing incidents · 2026-09-29
• Postmortem culture: learning from failure · 2026-09-29
• Evolving the SRE engagement model · 2026-09-29
• Contingency Planning Guide for Federal Information Systems · 2026-09-29