Agile + User Experience: How to navigate the Agile landscape as an UX Practitioner
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 practitioners often play multiple roles but sharing these across a team improves quality and velocity.
-
•
Embedding one UX member per scrum team works for small teams but can limit specialized UX focus.
-
•
A shared UX service team enables fluid support across multiple scrum teams and encourages swarming.
-
•
Attending only necessary agile ceremonies avoids overloading UX practitioners while maintaining alignment.
-
•
UX work ahead of development aligns with agile when done collaboratively during discovery and exploration phases.
-
•
Writing clear, scoped UX Jira tickets with acceptance criteria improves transparency, predictability, and stakeholder buy-in.
-
•
Decomposing UX work into manageable sprint-sized tickets helps improve delivery cadence and planning.
-
•
Effective documentation for accessibility ensures all team members, especially newcomers, understand domain context.
-
•
Using Confluence or similar tools as a centralized repository makes UX knowledge easily accessible and maintainable.
-
•
Creating video walkthroughs of UX flows aids comprehension across non-design teams and clients.
Notable Quotes
"If we can do many of these UX roles, we’re unicorns, but it still takes the same amount of time."
"A smaller agile team may require less documentation but has less scope and velocity impact."
"A shared UX service team can swarm to support different scrum teams as needs arise, increasing impact."
"UX work done ahead of development is not un-agile; we draft blueprints before building."
"Tech, business, and UX should collaborate through discovery, exploration, build, and evaluation phases."
"A good UX ticket is just like any other ticket — clear title, description, acceptance criteria, and scope."
"It’s really helpful to ask for meeting agendas in advance to attend only ceremonies where UX dependencies exist."
"If it’s not on Confluence, it doesn’t exist — having a living document repository is critical."
"Recording videos with voiceover to walk through user flows has become invaluable for sharing complex scenarios."
"Trust your UX team to represent each other when attending different scrum teams’ ceremonies."
Or choose a question:
More Videos
"We define knowledge management as a dynamic, systemic, and agile approach to creating, capturing, storing, and sharing knowledge."
Sean Baker Sara RomanoskiWeaving Knowledge Management into the Fabric of Our Design Practice
September 11, 2025
"You have to find ways for people to practice so they can learn without destroying projects."
James Wieselman SchulmanResearch is a team sport: advancing the work when everyone does the research
March 11, 2026
"Followers believe they don’t have power, but actually hold enormous power to enable leadership."
John MaedaMaking Sense of Enterprise UX
June 9, 2016
"The question is not whether AI is useful. It is. The question is what role should AI play."
Joy KendiMwitiDeciding when to automate: Integrating AI in high-stakes systems
June 9, 2026
"We need everyone to roll up their sleeves and be a part of the creative process to spark innovation and even delight."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"How am I supposed to do that? is a good question to reflect impracticality without defensive triggers."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
"In enterprise, we’re moving from systems of record, to systems of engagement, to systems of assets where context drives experience."
Greg PetroffEverything is About to Change: Software as Material
June 8, 2016
"People were pushed but had no idea what was expected from them — adaptability was lacking."
Niko LaitinenAdaptable Org Design for Resilient Times
June 10, 2021
"If you find yourself doing a lot of things that aren’t in your job description, that might mean you’re doing leadership."
Peter MerholzThe Trials and Tribulations of Directors of UX
July 13, 2023
