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
"The relational dynamics of knowledge are shifting from hierarchical and linear to relational and plural."
Jemma AhmedResearch at an inflection point: Adapting to a new era of collaboration, equity, and innovation
March 11, 2025
"We had no recipe, no formula, just vibes."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"By summer, there had been zero cases of COVID on farms employing temporary foreign workers in BC."
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"Nobody is going to be satisfied by insight-shaped answers or high-level summaries masquerading as breakthroughs."
Laura KleinHuman vs. machine: Testing AI’s ability to synthesize and analyze research
March 11, 2026
"Designing a metric starts with the goals, not the metric itself."
Alberto FerreiraMaking it Count: Developing a custom digital metric framework that works
October 15, 2021
"It’s the best way, absolutely best way, to unlock all the goodness in our content."
Louis RosenfeldHow to use the Rosenbot
March 16, 2026
"One of the most important parts of any successful research study is your research sample."
Noah BondRedefining truth and inclusivity: Navigating data ownership and ethical research in the age of disinformation
March 11, 2025
"Democratization means people without 'UX researcher' in their title are doing the research work—a 4:1 ratio compared to formal researchers."
James LangHopeful Futures for UX Research
January 30, 2026
"I was able to create user segments to analyze sustainability-related user journeys and identify gaps."
Amy ParnessScaling Sustainability: Complementary strategies that drive long-term success
May 29, 2025
Latest Books All books
Dig deeper with the Rosenbot
How have foreseeable harms in social media and gig economy platforms been linked to power imbalances?
What role do psychological safety and coalition-building play in surfacing invisible workplace issues?
What are the benefits and challenges of pairing engineers and designers in small, focused pods for product development?