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

Uncertainty & the Scaled Agile Framework (SAFe™)

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

What is the connection between Uncertainty and the Scaled Agile Framework?

Uncertainty is one of the core reasons we need to be agile. Different modes of Business/Requirements/Technology uncertainties impact our economic costs in product development – especially the potential impact of risk. The first principle of SAFe™ is “Take an economic view”. I frequently use my “uncertainty filter glasses” to take an alternative economic view. I find it helps Scaled Agile/SAFe™ practitioners/leaders understand both the need for Agility as well as examine various work system design considerations. In this article, I introduce the Stacey Matrix which is one of my favorite models for understanding the uncertainty landscape as well as the implications of uncertainty on various specific SAFe™ design decisions.

Making it Concrete – The Stacey Uncertainty Matrix and its relation to the Scaled Agile Framework

stacey1

As I wrote about at some length in Risk-Aware Product Development (a.k.a Agile) explaining the concept of Requirement/Business/Technology uncertainty is one of the first things I do with most audiences I meet for the first time. In a Leading SAFe/SPC class this typically takes place in the first module when we go over the need for SAFe. This is not a core part of the materials but I take the time to explain it anyhow and then find myself referring back to it throughout the workshop.

The first layer of realization is that our problem with the classic approaches to product development is that they were built for complicated endeavors but not complex ones.

Then we layer on more interesting realizations like the fact that for some endeavors like those approaching the “Anarchy”/”Chaos” domains probably the best approach would be a “Skunkworks” style cross-functional co-located fully empowered small team. As you grow a bit farther from Anarchy you can scale agility using an approach like the Scaled Agile Framework. At these levels of uncertainty/risk the trade-off of distributed teams, distributed PI Planning, system team, component teams, and shared architects/UX MIGHT make sense and are worth considering.

As you approach the simpler domain sometimes even the alignment rationale for “whole train” PI Planning can be reconsidered. Is that SAFe™ heresy? maybe. But I find that telling people “Whole ART PI Planning” is mandatory is less effective than showing them WHEN it has a better economic impact. (BTW as you grow in complexity/uncertainty you also need better people that are more engaged – which the Whole ART PI Planning helps with as well)

In general, this thinking helps leaders at these workshops grasp the various economic levers that go into tailoring a SAFe™ implementation. I find this disarms some of the resistance you get when people feel something is “a must”. Using this approach they typically go out with a stronger conviction to avoid some compromises and a better feeling about the compromises that do make sense.

To take another example of how I use the uncertainty matrix during SAFe™ training/implementation discussions – SAFe™ talks about a hierarchy between ART Product Management and the Product Owners working with the teams. A typical and sensible question people have is “Who should wear the Product Owner hat?”. Using the uncertainty matrix, we realize that in some cases the Product Owner should be a Product Manager (probably the top two quadrants of the matrix) and in some other cases, he can also be a more technical leader (Especially on the far right side of the matrix). As the typical organization, I work with is struggling to fill those Product Owner roles, this realization helps them deploy their people more effectively in a way that minimizes the risk of ineffective feedback loops due to the wrong individuals being in the tight Product Owner loop.

 

In summary

Understanding uncertainty and its attributes and implications is in my view and experience a critical step of buying into the need for agile as well as gaining the ability to design an effective agile approach for your context. Presenting the Stacey Matrix and trying to map it to your reality is one technique I used to help people gain this understanding. Using it as a decision filter/design criteria for further SAFe™ tailoring questions complements this initial presentation/exposure and grounds it. If you are teaching Leading SAFe™/SPC classes, explaining the need for agile to leaders/executives, or working with an organization to implement a scaled agile approach, I believe you will see improved results if you add this technique to your toolbox. I know I have.

Subscribe for Email Updates:

Categories:

Tags:

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