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
"People on the project were reporting back to management in their silo, not talking to one another."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"If you have somebody on your team for three years, for five years, that’s amazing from a longevity perspective given enterprise legacy and complexity."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"We share the inconvenience of meeting times across time zones, alternating so no one team always bears it."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"The collaboration cycle requires following standards for accessibility, content, design system usage, and IA or you don’t launch your product."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Move fast and break things doesn’t work when you’re designing for cancer patients or disaster victims."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"As the delivery driver, I connected the dots, got people briefs, and sometimes said no to lofty leadership requests."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Creating and holding space is like putting bumpers up in bowling so people know they won’t fail if they engage."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Regulations are design problems, not just technical ones, influencing how we create products and experiences."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"As your design practice matures, your design ops team will reach inflection points, and it’s okay to flip the coin and explore the other side."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
