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
"Titles mean different things at different companies, so asking about expectations for levels is critical."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles (Videoconference)
February 22, 2024
"Users initially were excited about AI, but six months later, there was more dissatisfaction and frustration despite quantitative time savings."
Jennifer Kong[Case study] Journeying toward AI-assisted documentation in healthcare
June 5, 2024
"Reports alone don’t build empathy because you don’t get close to users by reading a report."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"Some teams went right into brainstorming based on what they remembered from observations without documenting or analyzing the data."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Show don’t tell was really critical for getting buy-in from stakeholders."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"Listen for the 10% truth in the difficult person’s perspective and build on that."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
"We automated our staffing records and updated our staffing score weekly, watching it grow from 44 to nearly 80."
Patrick CommarfordDesign Staffing for Impact
January 8, 2024
"The impact of design ops isn’t as easy to define or predict like other business value measures."
Frances YllanaTheme 2 Intro
September 24, 2024
"Draw your ideas, even if you’re a words person; it unlocks new connections and thinking."
Mujtaba HameedFrameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
March 26, 2024