Organizational Evolution
Organizational Coaching +
Technical Coaching
8
People involved
2 Technical Coaches + 2 Agile Coaches
Empowered PO
Led by product individuals
Scrum
Dynamics
Cadence and Improvement
Challenge
When Product and Technology fail to make decisions together, the product suffers.
- Difficulty making collective decisions between Technology and Product.
- Lack of alignment on priorities and working dynamics.
- Impact on product outcomes and internal team morale.
- Need to restore collaboration and delivery cadence.
Goal
Improving collaboration and delivery: clear priorities, shared decisions, and coordinated teams.
Approach: Organizational + Technical Coaching
Scope: Product, UX, Business,
Solution
Diagnosis, structure, and spaces for improvement to sustain change
- Diagnosis & Roadmap
We assessed the current state of the teams and their dynamics to propose a concrete path for evolution.
- Scrum + Cross-Functional Teams
Teams capable of collectively deciding on priority, scope, and quality, with clearly defined roles
- Continuous Technical Improvement
Code improvement sessions: addressing real challenges through hands-on practice, changes, and shared learning.
Practices
What did we implement?
- Scrum
- Product Discovery
- Role-based Communities of Practice
- Pair and Mob Programming
- Refactoring
- Test Automation
Technologies
* Python * Flutter
Outcome
Unified backlogs, authentic retrospectives, and increased team engagement
Unified backlogs
Design + product + development
Product Management incorporated key practices: backlog management, definitions, acceptance criteria, and validation.
Continuous improvement
Retrospectives and communities of practice
The team began working with regular retrospectives and sustained spaces for improvement.
Planning
Collaborative process
The development department became actively involved in short-, medium-, and long-term planning, strengthening collaborative decision-making.