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:

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