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."
Or choose a question:
More Videos
"All our components can be data bound so the developer can point to any data source like CMS or JSON to populate UI elements naturally."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"There are 700 software providers selling to two million agents; most didn’t work until they did."
Greg PetroffDesign is the Differentiator: Bringing New Design Innovations to a Very Antiquated and Very Large Industry
June 9, 2021
"How am I supposed to do that? is a good question to reflect impracticality without defensive triggers."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
"Our purpose is to enrich people’s lives with technology, focusing on how to use—not just what to buy."
Sara Asche Anderson Jamie KaspszakNot Your Ordinary Re-Brand: Design's Path to Driving Customer Obsession at Best Buy
January 8, 2024
"We don’t talk about sustainable choices or green, we call it efficient to not get in the way."
Tristin OldaniTurning awareness into action with Climate UX
January 16, 2025
"In a hyperconnected world, design leadership is under constant personal inspection, making kindness and empathy really hard."
Erin Hoffman-JohnThis Game is Never Done: Design Leadership Techniques from the Video Game World
November 6, 2017
"Mobile screen readers can confirm basic accessibility but desktop testing is still needed due to differences across tools."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Great practices help you do more with less and work smarter, not harder."
Michelle MorrisonPractice What You Preach
January 8, 2024
"Creativity, accountability, and authenticity will be the new markers of humanity alongside AI."
Jonathan Fairman Kevin JohnsonIntegrating generative AI into enterprise products: A case study from dscout
June 5, 2024