Architettura software sbloccata in un'azienda medicale: da completion rate al 52% e software fermo da 12 mesi a 113% e progetto completato in due.

Software stalled for 12 months. Finished in two.

A team of five people in a medical company that is part of a multinational group. Everyone worked in complete autonomy, without coordination and with open conflicts between the senior figures. A piece of software under development had been stuck for a year. Six months of intervention, organised in four parallel phases.

  1. 01 / 04

    The situation

    • Each team member worked alone, from the beginning to the end of every project
    • Fragmented tracking across Excel and Azure DevOps, no structured planning
    • Open conflicts between the senior figures — the team saw the other departments as adversaries
    • Completion rate at 52% — software stuck in development for 12 months
  2. 02 / 04

    Technical training

    • TDD, BDD, DDD, CQRS and Event Sourcing on sample code, then on production code
    • SOLID principles and object-oriented programming
  3. 03 / 04

    Process training

    • Analyst trained as Product Owner: backlog, refinement, planning
    • Customer Support trained as Wellbeing Owner: meetings, retrospectives, conflict management
    • Joint definition of the team’s operating model
  4. 04 / 04

    Hands-on support and pair programming

    • Two months of 1:1 support and support for the whole team to consolidate the new process
    • Pair and mob programming sessions — the blocked software completed in 2 months

The results

  • +117%completion rate (from 52% to 113%)
  • 12 → 2months to complete the blocked software
  • 4/5team satisfaction at the end of the intervention