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
"Consistency is so important that sometimes even consistency in failure works if it means I only have to learn the workaround once."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"Evaluations and promotions can be nebulous and awkward, especially in collaborative design work."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"We needed to revise our plan; we couldn’t just keep adding talented folks and hope everything falls into place."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"Companies today are embracing these principles, seeing the value of user connection and self-actualization for business success."
Daniel GloydWarming the User Experience: Lessons from America's first and most radical human-centered designers
May 9, 2024
"AI systems can present speculative connections as established facts, so confidence ratings are critical."
Patrick BoehlerFishing for Real Needs: Reimagining Journalism Needs with AI
June 10, 2025
"Many customers struggle to get anyone to listen to actual insights because of the volume and complexity of raw video data."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"The future of our technology cannot and should not rest solely on the ethics of individual designers."
Alexandra SchmidtWhy Ethics Can't Save Tech
November 18, 2022
"Strategic friction is about where you apply friction deliberately to create insight and transformation."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"We’re literally using AI to help AI build AI, including bias detection and correction in the process."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
