Scaling Kanban Across Multiple Teams

Scaling Kanban

When multiple teams contribute to the same product or organization, a single board is no longer sufficient. Scaling Kanban involves creating a hierarchy of boards that provide visibility at different levels.

The Portfolio Board

A portfolio board sits above individual team boards and tracks high-level initiatives:

Portfolio Board:
Proposed → Approved → In Flight → Delivered

Team A Board:                Team B Board:
Backlog → Dev → Done         Backlog → Dev → Done

Each card on the portfolio board maps to multiple cards on team boards. This gives leadership visibility without micromanaging individual tasks.

Coordination Patterns

1. Dependency Boards

When teams depend on each other, track dependencies on a shared board:

Dependency Board:
Requested → Accepted → In Progress → Delivered

Cards here represent cross-team requests (e.g., "Team A needs API endpoint from Team B").

2. Standup of Standups

A 15-minute meeting with one representative from each team. The agenda is simple:

• What is flowing?
• What is blocked across teams?
• Are there new dependencies?

3. Shared WIP Limits

Set organizational WIP limits on the portfolio board:

• Maximum 3 initiatives "In Flight" at any time.
• This prevents the organization from spreading too thin.

Common Pitfalls at Scale

• Board sprawl -- Too many boards creates confusion. Keep the hierarchy to 2-3 levels maximum.
• Status theater -- Updating cards for reporting purposes rather than actual work. Keep updates lightweight.
• Ignoring dependencies -- Cross-team dependencies are the primary source of delays. Make them visible and track them explicitly.

Frameworks for Scaled Kanban

• Kanban Maturity Model (KMM) -- A structured approach to organizational maturity.
• Flight Levels -- David J. Anderson's model for multi-level Kanban (operational, coordination, strategic).
• LeSS / SAFe -- Larger frameworks that can incorporate Kanban at the team level.