SAFe and Scrum at scale: estimating across multiple teams

When a company grows from one to ten Scrum teams, estimation stops being a single-squad problem and becomes a coordination challenge. That’s where scaling frameworks like SAFe come in.

The scaling problem

With multiple teams:

An epic can span 5 different squads
Each squad’s estimates need to be consolidated
Cross-squad dependencies affect planning
Velocity varies between teams — a “5 points” doesn’t mean the same thing everywhere

SAFe: Scaled Agile Framework

SAFe organizes work into layers:

Team Level — individual squads running sprints
Program Level (Agile Release Train) — multiple squads aligned to a common goal
Solution/Portfolio Level — strategy and investment

PI Planning in SAFe

PI (Program Increment) Planning is SAFe’s central event. Every 8-12 weeks, all squads come together to:

Understand the product vision
Identify which squads work on which features
Estimate effort within each squad
Map cross-squad dependencies
Create a consolidated delivery plan

How to estimate during PI Planning

Estimation by squad

Each squad runs its own Planning Poker for the features assigned to it. The point scale is internal to the squad — you don’t compare across squads.

T-Shirt sizing for features

At the program level, T-shirt sizing is commonly used to estimate features:

Product Management presents the feature
Squads assign a size: S, M, L, XL
This helps with allocation planning without getting into technical details

Normalizing estimates

Some teams use Normalized Story Points — adjusting each squad’s velocity by a factor based on historical data, enabling fairer comparisons.

Cross-squad dependencies

This is the biggest scaling challenge. When Squad A needs to finish something before Squad B can start:

Map it visually — use a dependency board
Estimate the impact — how much does a delay in Squad A affect Squad B?
Negotiate priorities — Squad A may need to move their delivery forward
Communicate risks — stakeholders need visibility into dependencies

Alternatives to SAFe

LeSS (Large Scale Scrum)

Lighter than SAFe. Keeps pure Scrum principles, only scaling events and roles. No formal PI Planning.

Nexus

Scrum.org’s framework for 3-9 squads. Focuses on continuous integration across squads and includes a ceremony called the Nexus Daily Scrum.

Spotify Model

Autonomous squads organized into Tribes, Chapters, and Guilds. Less structure, more autonomy. Doesn’t always work outside Spotify’s context.

Tools for scaling

Jira Align — for PI Planning and portfolio management
Dev in Poker — for Planning Poker sessions across multiple squads
Miro/Mural — for visual dependency mapping

Conclusion

Scaling agile estimation requires more structure, not more bureaucracy. The key is maintaining each squad’s autonomy while building communication bridges between them. SAFe, LeSS, or Nexus — pick the framework that best fits your organizational culture.