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
"Denying the body is not an antidote to the suffering of the world. When we protect our rest, we protect our dreaming."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"If you don’t have enough information to prioritize, put the items on a dartboard and throw a dart to start the conversation."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars) (Videoconference)
June 13, 2024
"Sense-making is a motivated, continuous effort to understand connections and act effectively."
Nick CochranGrowing in Enterprise Design through Making Connections
June 3, 2019
"Sometimes it’s easier to pitch a change with a smaller group rather than rolling it out to everyone at once."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Quick wins help build trust and get stakeholders willing to work with you."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"We didn’t exploit the knowledge gap. Everyone was willing to say I don’t know. Can you help me?"
Nova Wehman-BrownWe've Never Done This Before
June 4, 2019
"Research thinking—not specific research methods—is foundational and evergreen for human researchers in AI."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"We made changes in the last three weeks that would normally have taken three years. Could we expect a COVID dividend?"
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"Sharing my story with the engineering director opened something; vulnerability builds trust."
Tutti TaygerlyMake Space to Lead
June 12, 2021
