Managing Multiple Agile Teams as a Delivery Manager

The Shift From One Team to Many

Managing delivery for a single team is hands-on. You know every story, every blocker, every team dynamic. When you scale to 3-5 teams, that model breaks. You can't attend every ceremony, can't solve every impediment personally, and can't maintain the same depth of context across all teams simultaneously.

The shift requires moving from direct involvement to system design. Your job becomes building the delivery system — the cadences, dashboards, escalation paths, and team capabilities — that enables multiple teams to deliver effectively with your oversight rather than your constant presence.

The Operating Model

Governance Cadences

Build a rhythm that gives you visibility without micromanaging:

Daily (15 min total, not per team):

• Scrum of Scrums: one representative per team surfaces blockers and cross-team dependencies
• You attend to listen, not to solve — note items that need your intervention

Weekly (60 min):

• Delivery review: walk the dashboard across all teams
• Focus on: blockers older than 48 hours, dependencies at risk, metrics trending wrong
• Outcome: clear actions with owners and deadlines

Fortnightly (per team, 30 min):

• Team health check: 1:1 with each Scrum Master
• Discuss: team dynamics, improvement experiments, impediments they can't resolve alone
• This is your coaching time — invest it in growing SM capability

Quarterly (half day):

• Cross-team retrospective: systemic issues that affect multiple teams
• Delivery strategy: what investments (tooling, process, people) will improve delivery next quarter?

Delegation Model

You cannot and should not solve every problem. Build a clear delegation model:

Scrum Masters own: Team-level impediments, ceremony facilitation, team dynamics, sprint-level decisions, backlog health coaching

You own: Cross-team dependencies, organisational impediments, stakeholder communication, delivery strategy, escalation resolution, resource allocation

Shared: Risk management, process improvement, tooling decisions, hiring and onboarding

Information Flow

Design information flow so you get the right signal without attending every meeting:

• Dashboard: Automated metrics give you real-time visibility (see Building a Delivery Health Dashboard playbook)
• Scrum of Scrums: Daily cross-team sync surfaces blockers and dependencies
• SM 1:1s: Fortnightly deep-dive on team health and dynamics
• Exception-based alerts: Scrum Masters escalate to you when: blocker exceeds 48 hours, dependency fails, team conflict they can't resolve, scope change impacts delivery commitment

Cross-Team Dependency Management

Dependencies between teams are the primary source of delivery risk when managing multiple squads. Make them visible and actively managed:

Dependency board: A shared board (physical or digital) showing all cross-team dependencies with:

• Providing team and consuming team
• What's needed and by when
• Current RAG status
• Owner responsible for delivery
• Escalation path if at risk

Dependency review: Weekly, walk the dependency board in the delivery review. Any dependency that's Amber or Red gets an immediate action plan.

Architecture alignment: Work with tech leads to reduce dependencies through better system boundaries. The best dependency is one that doesn't exist.

Scaling Your Attention

The 80/20 Rule for Delivery Managers

Spend 80% of your time on the 20% of issues that have the highest impact:

• The one team that's struggling (not the three that are fine)
• The one dependency that's critical path (not the five that are low-risk)
• The one stakeholder relationship that's strained (not the ten that are healthy)

The "Minimum Viable Involvement" Principle

For each team, determine the minimum level of your involvement needed for them to deliver effectively:

• High-performing team: Dashboard visibility + fortnightly SM check-in. You're available if needed but not actively involved.
• Developing team: Weekly delivery review attendance + active dependency management. SM handles day-to-day.
• Struggling team: Daily involvement until stabilised. Attend standups, coach the SM, resolve blockers directly. Temporary — the goal is to move them to "developing" within 2-3 sprints.

Building SM Capability

Your long-term leverage comes from growing Scrum Master capability. The better your SMs are, the less you need to be involved at team level:

• Coach SMs on impediment removal (don't just remove impediments for them)
• Build a SM community of practice where they learn from each other
• Give SMs increasing autonomy as they demonstrate capability
• Provide feedback on their facilitation and coaching (attend their ceremonies occasionally)

Common Pitfalls

Becoming a super-Scrum-Master: Attending every standup, solving every blocker, facilitating every retro across all teams. You burn out and teams never develop independence. Fix: delegate team-level work to SMs. Your job is the system, not the ceremonies.

Dashboard-only management: Relying entirely on metrics without human context. Numbers don't tell you about team morale, interpersonal conflict, or quiet disengagement. Fix: maintain regular human touchpoints (SM 1:1s, occasional team visits).

Treating all teams the same: Applying identical governance to a high-performing team and a struggling team. Fix: differentiate your involvement based on team maturity and current challenges.

Ignoring the organisational layer: Focusing only on team-level delivery while organisational impediments (slow hiring, inadequate tooling, unclear strategy) persist. Fix: spend at least 30% of your time on organisational impediments that affect multiple teams.

Measuring Multi-Team Delivery Health

Track at the portfolio level (across all your teams):

• Aggregate throughput: Total items delivered across all teams per sprint (trend)
• Cross-team dependency health: % of dependencies resolved on time
• Blocker resolution time: Median time from blocker raised to resolved (across all teams)
• Sprint Goal success rate: Aggregate across teams (target: >80%)
• Team health variance: Are all teams roughly healthy, or is one significantly struggling?

If one team's metrics are consistently worse than others, that's where your attention should focus — not equally distributed across all teams.

---

Download the [Dependency Matrix template](/templates) to track cross-team dependencies across your delivery portfolio.