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

SAFe is a Scaled Agile Framework, Not a Scaled Agile Methodology

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Last week this was a theme in the Implementing SAFe class Ofer Cohen and I ran in Waltham, MA.

We find it crucial when training new SAFe Program Consultants (SPCs) to emphasize that they should use SAFe as a framework, not a methodology.

First, what’s the difference between a framework and a methodology? I found this concise useful comparison written by Liz Keogh who I think highly of over at Quora

A methodology is a set of principles, tools, and practices which can be used to guide processes to achieve a particular goal.

A framework is a loose but incomplete structure that leaves room for other practices and tools to be included but provides much of the process required.

… Scrum could be considered a framework, as it leaves room for teams to choose their own technical processes, development roles, etc. XP might be considered a methodology, as it provides guidelines for all the same things that Scrum does, along with relevant technical practices. …

With this in mind, what we emphasize in the workshop is the options and choices you have when you Implement SAFe. Yes, some people look at SAFe and see a methodology that tells you how to estimate, prioritize, and plan, how your kanban boards should look like and what questions to ask in each Scrum of Scrums. We prefer to see all of those as a good set of options to start within many contexts, but not necessarily best practices that always work.

For example, we don’t believe story point estimation is necessarily the best way to estimate in all cases. We believe that sometimes it’s enough to just count stories.

The schedule/agenda for PI Planning is great, but we definitely inspect and adapt it on every implementation depending on the context and encourage SPCs and RTEs we teach to do it as well.

We always inspect and adapt the definition of Workflow of the Program and Portfolio Kanban boards on our implementations and we talk about it in class as well.

We always mention that SAFe’s approach to Weighted-Shortest-Job-First Cost-of-Delay-based prioritization is only one option and that some other interesting and useful and maybe even better ones for your context are available (and we point people to Don Reinertsen and Joshua Arnold )

What is the right Agile Release Train and Value Stream design? SAFe provides ways to help you design your implementation including some principles and considerations, but it doesn’t give you a hard and fast answer… This is one of my favorite sessions in the Implementing SAFe class actually.

Which elements of the SAFe Big Picture do you need? Which Spanning Palette or Large Solution elements does it make sense to use even if you’re using just Essential SAFe? And does it make sense to use Large Solution or Portfolio or Full? When?

In general, What is the right way to roll out at scale? Again, SAFe gives you some options and considerations to be aware of but doesn’t give you a concrete playbook.

Bottom line, both when it comes to how to practice SAFe as well as how to implement it, we prefer to consider it a very useful but flexible/incomplete structure that requires well-trained and experienced practitioners to successfully apply, and that’s a key design principle for our Implementing SAFe workshops where we train future SPCs.

Subscribe for Email Updates:

Categories:

Tags:

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