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 uses the Agile Release Train metaphor to synchronize multiple agile teams on a fixed schedule for incremental delivery.
-
•
SAFe initially excluded UX/design but now incorporates Lean UX as a bolted-on practice, often via a lean UX Center of Excellence.
-
•
There are typically not enough UX experts to embed one per agile team in large enterprises, necessitating a hybrid advisory model.
-
•
Discovery work within SAFe is often under-supported compared to delivery, causing challenges in shaping what to build.
-
•
UX work benefits from operating one or more iterations ahead of development, but this creates coordination and backlog challenges.
-
•
Embedding UX Architects at the program level alongside engineering architects improves early hypothesis validation and research.
-
•
There is confusion and overlap among roles like Product Owner, Product Manager, Business Analyst, and Requirements Analyst within SAFe.
-
•
Story pointing and capacity planning should include UX efforts, not just development, to improve realistic planning and resource allocation.
-
•
SAFe’s Dev-centric nature can marginalize UX work unless explicit efforts are made to integrate design activities visibly and measurably.
-
•
Visualizing and managing dependencies at scale through SAFe’s PI planning is valuable, but the framework can risk bureaucratic rigidity and loss of customer focus.
Notable Quotes
"SAFe’s Agile Release Train is a long-lived team of agile teams that incrementally deliver solutions in sync like a train leaving the station."
"While there aren’t enough lean UX experts for each team, having a lean UX Center of Excellence for each value stream helps embed UX advisory properly."
"The discovery aspect within SAFe’s portfolio is the hardest part to get right; many product owners lack the skills to determine what to build."
"We embed UX selectively in a few value streams and try to train others to balance research and design activities on their own."
"Working one to three sprints ahead for UX research helps validate hypotheses early but can create mini-waterfalls and handoff issues."
"In some organizations, UX Architects at the program level work with product managers to validate hypotheses and set design direction before PI planning."
"There’s often a disconnect because the people doing the research and conceptualization aren’t the same as those doing the development work."
"In SAFe, Product Owner and Product Manager roles can be confusing and inverted compared to other models, adding to role ambiguity."
"Story points should apply to UX work as well as development, helping make UX time and effort visible and planned for."
"SAFe risks becoming codified bureaucracy that sidelines the customer, but it holds potential if adapted to foster real business agility."
Or choose a question:
More Videos
"Policies must evolve to reflect the urgency of our situation."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"Time commitment for onboarding interns was close to 25%, maybe 50%, of at least two weeks, easing as they became familiar with roles."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Tell tight, brief stories of insights focused on impact, not on how you conducted your research."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"Mobile live captions can caption any sounds around the user in real time, making it a powerful accessibility tool."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"The program creates predictability so teams know when to submit questions and when findings will come."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Starting with specific, meaningful priority communities rather than homogenized personas leads to powerful breakthroughs."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"For many years, folks came to us with questions beyond design — about career paths, tools, skills, and intake management."
John DevanneyThe Design Management Office
November 6, 2017
"If they don’t give you a seat at the table, bring a folding chair."
Katy MogalBut Do Your Insights Scale?
March 12, 2021