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
"Research helps make a positive change on the product team and our end users."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022
"We want to bring our imaginations to building the worlds that we want."
Sarah BrooksTheme Three Intro
November 18, 2022
"Technology is reigning AI down on us across all industries, threatening our creativity and productivity."
Jon FukudaTheme One Intro
October 2, 2023
"Cohorts are a super duper fun way to engage with more of our community."
Bria AlexanderOpening Remarks
March 29, 2023
"If a security camera were recording, what would they see? Focus on facts, not stories."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"We had to allow people to grieve first before we could make a plan for healing."
Kyria Stephens Marlon KernerPower to Heal: Civic Design in the Aftermath of Tragedy
November 17, 2022
"Imposter syndrome feels universal here; even senior designers share that every project starts with feeling like you’ve forgotten how to do your job."
Caitlyn Hampton Monica Lee Jina YoonCompass 101: Growing Your Career In A Startup World
June 11, 2021
"Our job as design teams is to teach others what we do, not to feel insecure about sharing."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"Leadership often pressures teams to integrate AI without explaining why or how, which leads to confusion and frustration."
Rachel GarbExit Interview #7: Facing a blank slate in retirement when constraints are all you’ve ever known
August 5, 2026
