The Release Manager is responsible for orchestrating, governing and safeguarding the end-to-end release process across the CMS 2.0 program. The role ensures that releases from multiple vendors and projects are aligned, controlled and deployed in a consistent and reliable manner, minimizing risks to the platform and business operations.

Key Responsibilities

1. Multi-Vendor release coordination

2. Coordinate and align release planning across multiple vendors, domains and project teams.

3. Ensure a consolidated and realistic release calendar across CMS 2.0, align with CMS 1.0 releases if needed.
4. Facilitate alignment between interdependent deliveries and manage cross-team dependencies.

5. Act as the central point of contact for all release-related activities.

6. Release governance & process management

7. Define, implement and enforce the release management framework for the program.

8. Ensure adherence to release stages, further set up of quality gates and approval processes.
9. Maintain clear release criteria (entry/exit) and ensure readiness before deployment.

10. Drive continuous improvement of release processes through automatization and release practices.

11. Release impact & risk management

12. Own and facilitate the release impact assessment process across all involved parties.

13. Ensure that functional, technical, operational and business impacts are clearly identified and managed.
14. Support projects and vendors in applying the release impact procedure consistently.

15. Proactively identify risks (e.g. conflicts, data inconsistencies, performance issues) and ensure mitigation actions are in place.

16. CMS 1.0 & CMS 2.0 alignment

17. Ensure alignment and coordination between CMS 2.0 releases and ongoing CMS 1.0 operations.

18. Maintain visibility on dependencies and constraints between both environments.
19. Safeguard business continuity during the transition phase.

20. Provide clear reporting and oversight on combined release impacts across both platforms.

21. Communication & stakeholder management

22. Provide transparent and structured communication on release planning, status, risks and decisions.

23. Align with program governance bodies, project leads, vendors and operational teams and DGO’s.

24. Facilitate release boards or forums to support decision-making.

25. Monitoring & reporting

26. Track release progress, risks and issues across all stakeholders.

27. Provide consolidated reporting at program level.

28. Ensure post-release evaluation and lessons learned are captured and applied.

29. CI/CD pipeline governance & enablement

30. Define and promote a standardized CI/CD strategy across all vendors and teams contributing to the CMS 2.0 platform.

31. Ensure alignment on build, integration, testing and deployment pipelines to enable consistent and reliable releases.
32. Safeguard the integration of multiple vendor pipelines into a coherent end-to-end release flow.
33. Ensure that automated testing (unit, integration, regression) is embedded within the CI/CD pipelines to support release quality.
34. Monitor pipeline performance (e.g. build success rate, deployment frequency, failure recovery) and drive improvements.
35. Collaborate with architecture and platform teams to ensure pipelines are aligned with platform standards, security and compliance requirements.
36. Promote release automation and shift-left practices to reduce manual intervention and increase release predictability.

Context/Requirements:

Within the CMS 2.0 program, Atrias is evolving towards a multi-vendor, multi-domain delivery model on a shared central platform. This introduces significant complexity in coordinating releases across multiple stakeholders, ensuring alignment and safeguarding platform stability while maintaining continuity with CMS 1.0.