Critical Chain

Case study: Accelerate software release with Critical Chain + Agile

NuNet is developing an innovative computing platform aimed at networking private computers for various applications, ranging from training Machine Learning solutions and LLMs to scientific research projects demanding high computational power.

Already a fan of Agile methods, the Critical Chain allows NuNet for better resource allocation, focusing efforts on tasks critical to deadlines while ensuring reliable release announcements.

Agile methods help improve collaboration within a team and better distribute roles and tasks. However, when stepping back, one of the major weaknesses is losing the overall vision, particularly the emergence of bottlenecks. Indeed, teams are rarely perfectly dedicated and autonomous.

Interdependencies between skills, projects, and sub-projects disrupt the daily workflow of teams and the prioritization of the right topics.  

This is where the Critical Chain comes into play. NuNet's work initially involved defining the appropriate grouping of tasks, or "issues" in GitLab terminology, to create work packages and establish critical chain schedules by milestone. This approach highlights the critical work packages and, therefore, the "issues" to prioritize during kanban board reviews.  

The fever chart helps track the overall progress of the project and its criticality.  

The entire open-source project is visible here.  

NuNet is now deploying the Critical Chain across all its projects, adapting it to its Open Source DNA. Combined with Agile, the teams now benefit from a framework that allows them to know what to do, raise alerts at the right time, while maintaining flexibility.  

This flexibility is at the core of the solution: experts can discover new topics to explore and new problems to solve. The Critical Chain, thanks to its buffers, helps absorb some of these uncertainties while maintaining a cohesive overall structure.  

If you'd like to learn more, NuNet explains it best.