Before
LEADINGAGILE
- Over-architecture and future-proofing created long lead times.
- Introduction of complex content management drove complexity slowing down the development of new features.
- Heavy integration cycles and coupling between meant infrequent releases.
- A large percentage of engineer’ time devoted to bug fixes and security remediation.
With
LEADINGAGILE
- 93% test coverage creating safety to refactor the complex applications and decreasing defects by 70%.
- 55% reduction in lead time and a 9X improvement in cycle time.
- More time spent on value add work with a 75% decrease in waste.
- Teams successfully leveraging CI/CD, DevOps, Test Driven Development in their development workflow.
“Our application now works for us. It used to be the other way around.”
Our Approach
We understand the complexity of the changes involved to make lasting improvements. Over the last 15 years, we’ve refined our approach to take into account the organizational, human, and financial realities that often stand in the way of making change in large complex organizations. Our approach break the big changes into progressively smaller independently valuable units that can be planned, managed, and measured. We start getting results in months not years and use early successes to fuel future initiatives.
1. Break Dependencies Between Teams
Analysis comparing the code structure with the team structure to identify how the monolithic code base should be broken up to allow teams to work without having to coordinate with other teams. Strategic refactoring of the legacy code to establish stable APIs and contracts at the boundaries, reducing the delays and costs associated with integration.
2. Recover Productivity Within Teams
Our team established a new way of working by working alongside existing teams, allowing them to learn by doing with targeted coaching along the way. As work was completed on new features, the code was refactored bit by bit to drive out complexity and increase test safety, improving productivity over time.
3. Solidify Lasting Change
With health restored to the code base and the existing teams working in the new system, it was important to ensure that the application wouldn’t regress over time. New talent selection and screening processes were implemented, enabling the client to build teams and select vendors that would maintain and continue to improve the application’s health.