A different approach to estimations in SAFe


SAFe™ (The Scaled Agile Framework) uses Story Points throughout the various levels as its estimation currency. This is covered in the “Story” article on the SAFe site. This is a pretty standard practice in organizations scaling agile these days. If you dive a bit deeper into how this is done in SAFe you will see that actually the story points used in SAFe are quite similar to “Ideal Developer Day” as this helps the teams align to a common baseline and support a rational economic ROI discussion at the level of Features/Capabilities that require effort from more than one team or haven’t even been mapped to a specific team yet.

An alternative to using Story Points at the team level that is interesting to look at especially as Kanban is becoming a first-class citizen of the SAFe world is to use NoEstimates.

In essence, this means not trying to estimate the size of the work just slicing work into a size that we can bite on and turn around quickly. To get a quick grasp cards-legend-non-explicit-rotated-b43a891a4ea2f2300bc84fcbee6c3bb6of it think of replacing your classic Fibonacci planning poker cards with a set of cards saying 1, TFB (Too Frighteningly Big), NFC (No Faintest Clue). This approach is rising in popularity among Kanban/ScrumBan practitioners – We’ve been looking at the “Iteration Planning” process for years trying to address some of its wastes/tensions.

This “No Estimates” inspired approach to story estimation in PI Planning has a couple of benefits:

  • It is faster – which comes in handy during PI Planning.
  • It forces teams to slice into smaller stories which is better.
  • It is naturally easier to baseline/align multiple teams around the same definition. (BTW a 1 here would be something like a 3 or 5 in the classic SAFe velocity calculation – a story that takes the team about 3 days to develop and 3 days to test)

Iteration Planning becomes even easier – Just understand your velocity and how many stories you can fit. Minimal time is spent estimating.

There are a couple of challenges though. Forcing the team to split their whole Feature into small 1-size stories including those that are only going to be pulled in later iterations in the PI might be a waste of time.

Another challenge is how to make rational economic decisions at the Feature/Capability and even Epic level without estimates. #NoEstimates die-hards say it doesn’t make sense to estimate even at this level, not just the stories level. I’m not convinced. What I typically do in cases where teams stop estimating story sizes is just use story counts as the currency at the higher levels. So instead of saying “This seems to be a 20 Story Points Feature” we would say “This Feature seems to be something around 20 stories” meaning we ESTIMATE it will map to about 20 stories when we eventually slice it. We DON’T slice it to stories in order to estimate. We reach that estimation using a classic relative estimate approach like Planning Poker / Team Estimation Game. This is actually something that helps with the first challenge as well. Knowing that we’re dealing with a Feature that we think has about 20 stories and that we identified 7 stories for the first iteration and 4 stories for the second, we might say something like there are around 9 stories more for the third iteration or even better – let’s look at the remaining chunk and compare that to our feature estimation scale and see how many stories we think there are there.

Of course, if we think there are dragons (a.k.a dependencies) hidden in this remaining chunk we should make the effort to slice it into smaller stories and work out the dependencies/scheduling with the other teams on the train.

I’ve done this with clients in the trenches. Based on this experience, I consider this alternative approach to estimation a legitimate alternative to Story Points estimation at the SAFe Team Level.

This blog post was originally posted on Yuval’s personal blog back in 2016.  

Subscribe for Email Updates:



Managing Risk on Agile Projects
Built-In Quality
Lean and Agile Techniques
Jira Plans
Agile Testing Practices
Scrum Master
Continuous Integration
Agile Release Management
Systems Thinking
Continuous Delivery
Agile Release Planning
Professional Scrum Product Owner
Process Improvement
Continuous Planning
Acceptance Test-Driven Development
Continuous Improvement
Hybrid Work
Program Increment
Agile Product Ownership
Story Slicing
Lean Agile Management
The Agile Coach
Risk-aware Product Development
Agile Product Development
Agile Israel Events
Perfection Game
Agile India
Enterprise DevOps
Release Train Engineer
Agile Basics
Nexus and SAFe
Applying Agile Methodology
The Kanban Method
Advanced Roadmaps
Large Scale Scrum
Agile Project
ART Success
Implementation of Lean and Agile
Daily Scrum
Software Development
Agile for Embedded Systems
Agile Israel
Scrum Guide
Nexus Integration Team
Lean and Agile Principles and Practices
Lean Startup
Accelerate Value Delivery At Scale
Agile Project Management
Kanban Basics
Entrepreneurial Operating System®
Continuous Deployment
Introduction to ATDD
RTE Role
Games and Exercises
Artificial Intelligence
Lean Software Development
Professional Scrum with Kanban
Value Streams
Kanban 101
Agile Delivery
Lean Agile Organization
Agile Development
Agile Games and Exercises
Lean Agile Basics
Business Agility
System Integration Environments
Reading List
Agile Games
Lean Agile Leadership
Software Development Estimation
Agile Exercises
Product Management
Legacy Enterprise
Rapid RTC
Nexus and Kanban
SAFe Release Planning
lean agile change management
Agile in the Enterprise
Operational Value Stream
Principles of Lean-Agile Leadership
ScrumMaster Tales
Kaizen Workshop
Jira Cloud
Managing Projects
Agile Techniques
Engineering Practices
PI Objectives
Lean-Agile Budgeting
A Kanban System for Software Engineering
Quality Assurance
Lean Risk Management
Scaled Agile Framework
speed at scale
Elastic Leadership
Portfolio for Jira
Scrum Primer
Product Ownership
Sprint Iteration
Sprint Retrospectives
Lean Agile
Kanban Kickstart Example
Achieve Business Agility
Lean-Agile Software Development
Development Value Streams
IT Operations
Iterative Incremental Development
Introduction to Test Driven Development
Sprint Planning
Implementing SAFe
ALM Tools
Agile Risk Management
Releases Using Lean
Agile and DevOps Journey
speed @ scale
Pomodoro Technique
Agile Assembly Architecture
Agile Mindset
Test Driven Development
Risk Management on Agile Projects
Scrum Master Role
An Appreciative Retrospective
Scrum and XP
PI Planning
System Team
Kanban Game
Limiting Work in Progress
Professional Scrum Master
Agile Contracts Best Practices
Agile Program
Change Management
Lean Budgeting
Scrum With Kanban
Legacy Code
Certified SAFe
System Archetypes
Risk Management in Kanban
SAFe DevOps
Scrum Values
What Is Kanban
Agile Community
Effective Agile Retrospectives
Coaching Agile Teams
Agile Outsourcing
AI Artificial Intelligence
Manage Budget Creation
Nexus vs SAFe
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart