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
"Practical ops is about getting stuff done because it’s our job to scale the organizational ability to design and amplify the work of designers."
Bria AlexanderTheme Two Intro
October 3, 2023
"When the pandemic hit, those in the resilient 'yellow' zone had enough reserve to readjust and come back."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"On lower layers, research spaces are limited and focused, while at higher layers, problem spaces are ambiguous and require holistic approaches."
Cornelius RachieruHandling Complexity: Framing a Scale of Design
June 9, 2021
"WCAG does not apply to native mobile apps, which is how slow progress can be on this topic."
Megan Clegg Michael Haggerty-Villa Alexis MorinSpace for Everyone: Reframing Accessibility Through a Wider Lens
June 10, 2021
"Starting a new job with no map felt lost; so I built a new map as my BYO orientation."
Saara Kamppari-MillerCartography for Design Communities
September 10, 2025
"Legislation like the US executive order on federal customer experience has helped us rebuild trust in government."
Kara KaneTheme One Intro
November 16, 2022
"Designers need to switch hats when working with people who aren’t trained designers — mentoring is essential."
Natalia RadywylCo-Designing New Power in Australia's Public Sector
November 16, 2022
"Google’s photo algorithm mistakenly tagged Black people as gorillas, which was called out by Jackie Elsene."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"We invented the ‘prompt deep dive’ technique to spend lots of time on one prompt to deeply understand it."
Peter Van DijckBuilding the Rosenbot
June 4, 2024
