While increasing reliability and reducing the stress of frequent releases.
Go enabled Nokia teams who were implementing Continuous Delivery, to increase release frequency of releases and reduce release cycle time while delivering tangible business value predictably and reliably.
“Business knows all too well that slower and larger releases are buggy and unreliable. With Go we have frequent releases of smaller amounts of functionality. This avoids all the pressure, escalations, and rollbacks, while enabling reliable, predictable releases. They really see a value in this.”
- Team wanted to implement Continuous Delivery as a core development practice.
- High-pressure ‘Release Deadlocks’ – balancing delivery of big scope, new features and resolving bugs involving multiple stakeholders and escalations
- Lengthy, manual, risky deployment steps to production.
How did Go help?
- Eliminated release anxiety with traceability and visibility. “It was so easy for us to roll out the component. We deployed to production in the middle of the night, almost unattended.”
- Increased automation, decreased rollbacks. “It took some time to improve our automation. But on the other hand we saved time doing rollouts, rollbacks, as well as fire-fighting.”
- Increased release frequency with a robust, scalable build grid. “Recently we deployed a new component weeks before it had to go into production. And it was pretty easy to do it. The team had a big advantage to bene!t from feedback and make 10 changes in the last 2 weeks before the launch.”
- 66% reduction in average release cycle time for legacy components.
- New components are rolled out in half a day.
- Number of rollbacks have decreased by 2x.
- 20X increase in number of releases.
- 87% decrease in deployment costs for rollout to production.
Read the full Nokia Case Study (PDF)