A startup in the e-government sector with five people on the development team. Fragmented work, no testing, iterations that closed with 20% of the activities completed. The intervention rebuilt the way the team works, starting from coordination, moving through code quality and arriving at regular releases.
01 / 04
The situation
- Developers working in complete isolation, with no coordination
- Little or no testing — the tester was separate from the development team
- Iteration completion rate below 20% — 60 bugs a month
- Code reviews that were only formal, with no real quality control
02 / 04
Team collaboration
- Training and workshops on structured backlog management and iterative work
- Daily meetings for daily feedback loops and clear goals for each cycle
03 / 04
Code quality
- Microlearning on TDD and BDD with pair programming
- WIP limits and shared agreements on quality standards
04 / 04
Releases with real value
- Retrospectives with mandatory actions and structured refinement meetings
- Tech lab for shared technical training in the team
The results
- +350%completion rate (20% → 90%)
- -83%bugs per month (from 60 to 10)
- -80%development time per feature (from 5 days to 1)




