Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
SAFe or Sorry?
Summary
In his article for Forbes titled Understanding Fake Agile, Steve Denning refers to SAFe as “codified bureaucracy”. Jared Spool says it’s a “fast path to mediocrity”. But the Scaled Agile Framework (SAFe) is currently in use by many enterprise organizations like NASA, Capital One, FedEx, and the Department of Defense. With so many companies attempting to become as agile as Silicon Valley startups, SAFe is being adopted as a way to scale up Agile software development processes, and many UX teams are having to support it, whether they like it or not.
Key Insights
-
•
SAFe scales agile by organizing multiple agile teams into Agile Release Trains aligned on synchronized iteration schedules.
-
•
Lean UX is typically added to SAFe as an afterthought, creating a hybrid decentralized model where a UX Center of Excellence supports multiple teams.
-
•
Due to limited UX resources, embedding a UX person in every agile team is usually impossible; training team members and using design systems help alleviate this.
-
•
Program Increment (PI) Planning is a key SAFe event to visualize dependencies and align teams around shared work and schedules.
-
•
Working UX one or more iterations ahead of development is important to validate hypotheses but risks creating mini-waterfalls with handoffs.
-
•
Story pointing UX work alongside development stories can improve capacity planning and make UX effort visible to the teams.
-
•
Product Owner and Product Manager roles in SAFe can be confusing and sometimes reversed compared to other agile methodologies, causing role conflicts.
-
•
Smaller SAFe implementations (as low as 100-125 people) can still benefit from the framework, especially for managing inter-team dependencies.
-
•
Effective collaboration between UX, requirements analysts, and business analysts is crucial due to different focuses: user experience vs. business process.
-
•
A risk of SAFe is codified bureaucracy that may isolate agile teams from customers, potentially undermining true business agility.
Notable Quotes
"Each Agile Release Train is a long-lived team of agile teams that delivers solutions incrementally within a value stream."
"If something is not ready by the time the train leaves the station, then it catches the next train."
"There aren’t enough lean UX experts to collaborate with every team, so we create a lean UX Center of Excellence for each value stream."
"Our PI planning events are like 600 people strong, including representatives from across our 6,000 person company."
"Story pointing UX work would help us plan capacity and avoid being surprised by last minute discovery work."
"SAFe is very developer-centric and was originally designed for construction—the code production part of software."
"In SAFe, product owner and product manager roles are reversed from what some teams expect, which causes confusion."
"PI Planning really helps visualize dependencies between teams, which was invisible before."
"If the entire firm isn’t operating the same agile script, you won’t get the benefits of scaled agile."
"Steve Denning says SAFe is codified bureaucracy where the customer is almost totally absent."
Or choose a question:
More Videos
"Sometimes the solution perceives the problem in the eyes of users, especially in enterprise spaces."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"The team is passionate, creative, and innovative, building experiences that people love."
Jen Crim Jess Quittner Saritha Kattekola Alex Karr Gurbani PahwaCulture, DIBS & Recruiting
June 11, 2021
"Product manager is not the CEO of the product and I don’t think that’s a very helpful metaphor."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"We have to slow down hiring to be more thoughtful and deliberate about who we bring on the team."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"Sustainability is not just about the environment, it’s about community."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"Jamie Foxx spent 14 hours with his eyes closed to inhabit Ray Charles’ world."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Data is not just numbers; it tells us the story of student learning."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"If you frame it as poor first experience risks a negative impact on adoption, you get way more eyeballs and attention."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Friction isn’t just annoying; it’s a force that reshapes behavior and can slow or stop user flow."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
Latest Books All books
Dig deeper with the Rosenbot
How can research enablement free up time for researchers to focus on high-level strategic questions?
How does starting a vision in text before visuals improve the quality and buy-in of the vision?
How does Rally’s research infrastructure facilitate participant management and integration with enterprise data systems?