Summary
In 1993 Don Norman coined the phrase User Experience (UX), suggesting software be built with user’s needs at the core. In 2001, Agile was formally introduced as a framework to accelerate and improve software development. We’ve come a long way in 20 years, but there’s often still questions about how UX and Agile fit together. In this session we’ll share best practices we’ve found helpful in creating alignment, managing workflow, and improving outcomes. The goal is not to endorse a specific framework but to speak broadly to agile concepts and their application for UX practitioners in navigating the Agile landscape.
Key Insights
-
•
UX and agile are not prescriptive; teams must adapt them to their context.
-
•
Embedded UX practitioners improve communication and collaboration within agile teams.
-
•
Larger teams may benefit from a shared service UX model to address diverse project needs.
-
•
Attendance at agile ceremonies can significantly aid UX teams in understanding project dynamics.
-
•
Effective documentation, like UX tickets, enhances transparency and aligns team expectations.
-
•
Collaborative discovery and exploration phases are vital for effective UX integration into agile workflows.
-
•
Accessibility in UX work ensures all team members, regardless of experience level, can engage with the process.
-
•
Using tools like Confluence helps centralize documentation for broader accessibility.
-
•
Creating videos as part of documentation can clarify complex scenarios for stakeholders.
-
•
Continuous feedback and iteration are key to the success of UX in agile teams.
Notable Quotes
"Agile and UX are powerful forces that can sometimes be confusing to apply together."
"It’s important to remember that even if one person performs multiple UX roles, they still require time just like any other specialist."
"A smaller agile team may be faster, but the impact won’t be as great compared to larger teams."
"Our UX work guides the entire team, but it only does so when it’s written and distributed."
"If it’s not on Confluence, it doesn’t exist."
"Document documentation that can benefit a wider audience, not just those familiar with the domain."
"We should prepare our tickets in advance, creating a shell with the scope clearly defined."
"Videos have become invaluable to help teams understand complex scenarios, making our work more accessible."
"Documentation should evolve into living documents, continually updated with new information."
"Trusting your team is essential when establishing shared service models; efficiency relies on collaboration."
More Videos
"The urgency trap prioritizes outputs over relationships."
Rachael Dietkus, LCSWThe power to heal and harm
March 13, 2025
"I can actually start with secondary research and synthesizing what already exists."
Shipra Kayan Robert Kortenoeven Eileen TangEmerging principles for using AI in Design: What the product design team at Miro has learned from deeply integrating AI in their workflow
June 11, 2025
"You can create an information experience; it’s not just about the data."
Sarah CoyleDesign and Analytics with Sarah Coyle
July 30, 2020
"The assembly line approach created unmet needs and dysfunction within our team."
Christopher Taylor Edwards Valerie RoskeDesign as a Team Practice, A Practical Guide to Cross-functional Collaboration
September 30, 2021
"There's a clear correlation between team size and the presence of design ops."
Patrizia Bertini Alexandra Mengoni LeónPushing DesignOps’ Influence into New Global Markets
September 9, 2022
"Prioritization is a powerful tool because fundamentally, innovation is a problem-solving process."
Harry MaxPriority Zero: Some Things are More Equal than Others
June 9, 2016
"We want you to have a positive experience."
Louis Rosenfeld Bria AlexanderDay 1 Welcome
September 23, 2024
"The design industry has taught us that accessibility isn't innovative."
Alexis LucioScaling Accessibility Through Design Systems
June 9, 2022
"Hiring is difficult; it takes time to find the right fit for the team."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
