Pipeline di rilascio software: da zero funzionalità in sei mesi a trenta rilasci ogni due settimane con valore reale per il cliente.

Zero releases in six months. Then thirty every two weeks.

A leading company in the betting sector was developing a new product with 13 people. After six months of continuous work, not a single feature with real value for the end customer had been released. The problem wasn’t the quality of the people — it was the way they worked together.

  1. 01 / 04

    The situation

    • Zero releases made in 6 months of continuous development
    • Only 2 features delivered, with no value for the end customer
    • Activities assigned from above, workload distributed unevenly
    • Mostly manual testing, with no structured quality assurance processes

  2. 02 / 04

    Team collaboration

    • Training and workshops on backlog management and iterative work
    • Fair distribution of workload and team self-organisation

  3. 03 / 04

    Code quality

    • Microlearning on TDD and BDD applied directly to production code
    • Pair programming for shared technical growth and agreement on quality standards

  4. 04 / 04

    Continuous release focused on value

    • Product Owner trained for progressive, customer-focused releases
    • Continuous release pipeline with a trunk-based approach and collaboration between 4 teams

The results

  • 2 → 30features released every 2 weeks
  • 100%features with real value for the customer (from 0%)
  • 1.700%ROI in 12 months