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.
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."
Dig deeper—ask the Rosenbot:
More Videos
"Research is about being ready for anything, even what you didn’t imagine."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"Negotiating severance is absolutely possible; consider legal advice or coaching when doing so."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Meaningfulness is linked directly to what your organization cares about in terms of goals and priorities."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"We’re often stuck on a hamster wheel of short-term metrics like daily or monthly active users that don’t capture long-term success."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Behavioral turbulence happens when flow breaks down, causing chaotic and unpredictable user interactions."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"If you dug deeper into feedback, you'd find ways to address issues without a big change."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Designers have power. We get to decide who gets heard, who gets included, who gets excluded."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Employee experience and customer experience are inextricably tied—operationalizing design Ops impacts both."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Therapists create space for clients to reflect and discover insights in a safe environment."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
