← All case studies

Multi-Team Org: 20% to 100%+ in 6 Months

A Major SaaS Provider in the Healthcare Space · 2 Distributed Dev Teams

20%
Starting Point
100%+
Sustained After
6 mo
Time to Turnaround

The Situation

An engineering organization at a major healthcare SaaS provider with 2 dev teams — one based in India and the other distributed across North America — was struggling with delivery. Sprint completion rates were in the 20-40% range, with some sprints dipping below 20%. The organization needed a complete reset of how they planned and executed work across time zones and cultures.

The Approach

Starting in mid-2022, new practices were introduced across the organization. Rather than a top-down mandate, the approach was to implement changes incrementally and let the results speak for themselves:

  • Per-team capacity planning — each team planned sprints based on their actual available dev days
  • Cross-team coordination — dependencies between teams were identified and planned for up front
  • Proper story scoping — teaching teams what a well-sized story looks like: clear acceptance criteria, deliverable within a sprint, and structured as vertical slices through the stack
  • Transparent metrics — velocity and completion rates were visible to everyone, creating healthy accountability

The Results

Progress was steady rather than instant. Within 6 months, teams were consistently hitting 70-100%+ of their sprint commitments. By mid-2023, several sprints exceeded 130% of commitment — meaning teams had built enough predictability to pull in additional work when they finished early.

Sprint Completion Rate Over Time

S2
S3
S4
S5
S6
S7
S8
S9
S10

Deployment Confidence

Predictable sprints led to predictable releases. Over 52 weeks, the team executed 61 deployments with zero outages and only one rollback. When teams deliver right-sized, well-tested work, deployments stop being scary.

61
Deployments / Year
0
Outages
1
Rollback

Key Takeaway

Scaling these practices across multiple distributed teams requires patience and consistency. Each team adopted at their own pace, but the framework was the same: plan based on capacity, scope stories properly, track what matters, and hold the system accountable — not the people.

The compounding effect was powerful. As teams became more predictable, cross-team coordination became easier, which further improved delivery across the organization.