Alfa-Bank: controlled releases against a fixed deadline
Organised 13 releases in 10 working days before the change freeze: six backend/API services in B2C lending, banking integrations and coordination across teams. No post-release defects were registered from these releases.
Delivered before the freeze
In 10 business days in December 2025
Time taken to deliver 13 releases
Before the deployment freeze began
Post-release defects following these releases
Outcome of the 13 releases before the freeze
A deployment freeze was approaching in December 2025. The releases covered the B2C lending domain, with six backend/API services and integrations between banking systems.
As Head of Direction, I was responsible for organising development, releasing changes and service reliability. I coordinated analysts, developers, testing and adjacent teams, and managed priorities, risks and dependencies.
- Organised 13 releases before the deployment freeze began.
- Established release controls covering early release-version commitment, a mid-sprint review and readiness criteria.
- Included rollback plans and post-release checks in the process.
- Aligned work with architecture, infrastructure, security and adjacent teams.
The team delivered 13 releases in 10 business days before the freeze. No post-release defects were recorded following these releases.
Have a complex technology problem?
Let’s discuss it