Deployment management roles, competencies and organizational structures
Domain 3: Roles, competencies and organizational structures
This domain tests who does what and how team design affects deployment outcomes. Expect questions on accountability, competency gaps, and centralized versus decentralized models.
Core rules
- Deployment manager: coordinates the practice, maintains standards, plans complex deployments, and reports performance. Deployment practitioners perform build, test, and deployment tasks.
- Release manager: plans and controls releases and their availability. Change manager authorizes changes. Environment managers protect environment integrity. These roles can be combined in small organizations, but accountability must remain clear.
- Competencies include CI/CD tooling, scripting and automation, environment and configuration management, testing, risk assessment, stakeholder communication, and incident-ready troubleshooting.
- Structures: centralized deployment team for control, efficiency, and scarce skills; decentralized product teams for speed, autonomy, and end-to-end ownership; hybrid or platform team for shared pipeline and standards. Fit depends on service criticality, scale, regulation, and technical architecture.
Worked example
A bank runs 60 product teams. A central deployment team cannot keep pace, so it becomes a platform team owning the pipeline, environment templates, and deployment standards. Each product team embeds a deployment practitioner. A deployment manager remains accountable for cross-team scheduling and metrics. Change enablement pre-approves standard low-risk deployments. The reasoning: autonomy for routine work, central control for shared risk.
Traps
- Assuming the deployment manager personally executes every deployment.
- Confusing release and deployment accountability.
- Copying an organizational model without considering risk and scale.
- Ignoring automation competency in role design.