OKR template to execute effective decoupling of legacy monolith system
This OKR is centered on the transition from a legacy monolithic system to a more modern microservices architecture. The main objective is to effectively decouple the system, in which one of the specific outcomes outlined is to reduce the number of monolithic components by 30%.
To attain this outcome, certain steps have been proposed such as identifying which components can be redesigned into microservices, implementing and testing the newly created microservices, and developing microservices that replace identified monolithic components. The milestone of this step would be to achieve 90% functionality of these services.
Another aim is to ensure business continuity without interruptions during this transition process. To achieve this, an initiative has been laid out to implement a schedule for regular maintenance and updates, develop comprehensive testing procedures for the new services, and make contingency plans for potential disruptions.
The final aim seeks to equip and fortify the software team to handle these changes. The goal here is to train 75% of the team in modular programming languages. The initiatives for this outcome involve scheduling comprehensive training sessions, conducting evaluations and measurements of progress after said sessions, and identifying team members who may be lacking in skills in modular programming.
To attain this outcome, certain steps have been proposed such as identifying which components can be redesigned into microservices, implementing and testing the newly created microservices, and developing microservices that replace identified monolithic components. The milestone of this step would be to achieve 90% functionality of these services.
Another aim is to ensure business continuity without interruptions during this transition process. To achieve this, an initiative has been laid out to implement a schedule for regular maintenance and updates, develop comprehensive testing procedures for the new services, and make contingency plans for potential disruptions.
The final aim seeks to equip and fortify the software team to handle these changes. The goal here is to train 75% of the team in modular programming languages. The initiatives for this outcome involve scheduling comprehensive training sessions, conducting evaluations and measurements of progress after said sessions, and identifying team members who may be lacking in skills in modular programming.
- Execute effective decoupling of legacy monolith system
- Reduce number of monolithic components by 30% using microservices architecture
- Identify monolithic components viable for redesign into microservices
- Implement and test newly created microservices
- Develop microservices replacing identified monolithic components
- Achieve 90% functionality in new services, ensuring business continuity without interruptions
- Implement regular maintenance and updates schedule
- Develop comprehensive testing procedures for new services
- Initiate contingency planning for potential disruptions
- Train 75% of the software team in modular programming languages for maintenance
- Schedule and implement comprehensive training sessions
- Evaluate and measure progress after training
- Identify team members lacking modular programming skills