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
"You can leave a legacy in three minutes by giving a connection or sharing an insight—it doesn’t have to be grand."
Mark TempletonCreating a Legacy: the ultimate experience
June 9, 2017
"Customer voice lives in minds, not in artifacts. We want people to truly hear how customers think and what they value."
Dagmara KukawkaTiny team, moonshot impact: Democratizing research across continents
March 10, 2026
"If a client isn’t in the room when UX work happens, they don’t see the value and don’t understand it."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"Every research project is a chance to serve the whole organization and bring in missing perspectives."
Gregg BernsteinOpportunistic Research with Gregg Bernstein
July 11, 2019
"It’s not enough to just write down principles—they must be operationalized and made actionable for different teams."
Sarah WilliamsVerizon_A Framework for CX Transformation
January 8, 2024
"Many times when planning to hire, we first assess our team competencies to identify the necessary talent."
Ebru NamaldiDesigning the Designer’s Journey: Scaling Teams, Culture, and Growth Through DesignOps
September 11, 2025
"Try to observe the situation like a security camera—stick to factual, objective descriptions."
Joshua GravesWe Need To Talk: Addressing Unmet Expectations (Part 2 of 3)
April 28, 2025
"Don’t just run away from something. Make sure you are running towards something."
Renee ReidBecoming a ResearchH.E.R (Highly Enterprise Ready)
June 3, 2019
"Salary is the most objective data point we have, but many questions here are subjective, like satisfaction and design maturity."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
