Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

A different approach to estimations in SAFe

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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:

Categories:

Tags:

Operational Value Stream
Tips
Presentation
Lean Agile Organization
Certified SAFe
Lean-Agile Budgeting
What Is Kanban
Risk Management on Agile Projects
Lean Budgeting
Story Slicing
Agile Exercises
Agile Testing Practices
Continuous Integration
NIT
Product Ownership
ART Success
Agile and DevOps Journey
Kanban
Agile Games and Exercises
ScrumMaster Tales
Agile Product Ownership
POPM
Professional Scrum with Kanban
Lean and Agile Techniques
AI Artificial Intelligence
SA
Agile Community
Daily Scrum
Jira Plans
WIP
Scrum Master Role
A Kanban System for Software Engineering
Webinar
Professional Scrum Master
ATDD vs. BDD
Kaizen Workshop
Planning
Lean-Agile Software Development
Code
Accelerate Value Delivery At Scale
Continuous Delivery
Sprint Planning
Continuous Improvement
Applying Agile Methodology
LAB
IT Operations
Jira admin
Software Development Estimation
Agile Assembly Architecture
Agile Mindset
Value Streams
AI
Pomodoro Technique
Kanban Kickstart Example
Certification
Scrum Values
Agile Marketing
Advanced Roadmaps
Agile Techniques
Effective Agile Retrospectives
Lean Agile Basics
QA
Lean Software Development
Agile Development
Achieve Business Agility
Frameworks
System Team
SAFe Release Planning
Introduction to ATDD
Lean Agile Leadership
GanttBan
Product Management
agileisrael
Portfolio for Jira
Agile Release Management
Large Scale Scrum
RTE Role
Built-In Quality
ALM Tools
Agile Basics
Agile Release Planning
Agile India
Managing Projects
Jira
Agile Product Development
Principles of Lean-Agile Leadership
Systems Thinking
Covid19
SPC
Professional Scrum Product Owner
LeSS
TDD
Atlassian
lean agile change management
Lean Agile
Introduction to Test Driven Development
Nexus and Kanban
Agile
Agile Contracts Best Practices
Risk-aware Product Development
Managing Risk on Agile Projects
Self-organization
Jira Cloud
Legacy Enterprise
AgileSparks
BDD
RSA
Agile Program
Tools
ARTs
Agility
Acceptance Test-Driven Development
System Integration Environments
SAFe DevOps
EOS®
RTE
Amdocs
Kanban Basics
SAFe
Agile in the Enterprise
Agile Risk Management
Agile Outsourcing
Lean Startup
Program Increment
Lean and Agile Principles and Practices
Perfection Game
Nexus Integration Team
Agile Delivery
Manage Budget Creation
Coaching Agile Teams
ROI
Kanban Game
Scrum Master
PI Planning
ATDD
Implementation of Lean and Agile
System Archetypes
Scrum Guide
Quality Assurance
Releases Using Lean
Process Improvement
Continuous Deployment
Rapid RTC
speed @ scale
Kanban 101
Enterprise DevOps
Nexus vs SAFe
LPM
Legacy Code
Artificial Intelligence
Implementing SAFe
Limiting Work in Progress
An Appreciative Retrospective
The Kanban Method
predictability
Games and Exercises
Reading List
Lean Agile Management
Slides
Change Management
Video
Agile Games
Test Driven Development
Agile for Embedded Systems
Nexus
Agile Project
The Agile Coach
Engineering Practices
Release Train Engineer
Nexus and SAFe
Continuous Planning
Agile Israel Events
Agile Israel
Business Agility
Risk Management in Kanban
Sprint Iteration
Lean Risk Management
Entrepreneurial Operating System®
Atlaassian
speed at scale
Scrum With Kanban
Agile Project Management
DevOps
Scrum and XP
Scaled Agile Framework
PI Objectives
Sprint Retrospectives
Kaizen
Scrum Primer
Software Development
Scrum
Hybrid Work
Scrum.org
Iterative Incremental Development
Elastic Leadership
Development Value Streams
AgileSparks
Logo
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