An approach that integrates UX design practices within Agile software development cycles. Rather than completing all design before development begins, Agile UX runs design just ahead of development sprints, allowing rapid iteration based on feedback.
Common contexts
- Running discovery for sprint 4 while development builds sprint 2 features
- Attending sprint reviews to identify usability gaps before they compound across features
- Negotiating story points for design tasks alongside engineering tickets in sprint planning
Use when
Agile UX works best when you structure design to stay at least one sprint ahead of development — giving developers defined, validated designs while giving designers enough runway to do proper exploration. Make sure UX work has its own stories and acceptance criteria in the backlog, not just commentary on engineering tickets.
Avoid when
Agile UX becomes a liability when the team uses velocity pressure as a reason to skip validation — shipping untested designs sprint after sprint and calling it 'iteration' is just building the wrong thing faster. If there's no time for any feedback loop, you're doing waterfall with daily standups.
The 'just ahead' model only works if design has enough slack to react when research contradicts the plan — a designer with zero buffer is a designer who rubber-stamps whatever was already scoped.
Real-world examples
- Spotify's squad model embeds UX designers directly within cross-functional product squads so research and design happen within the same two-week sprint cycle.
- IBM adopted a continuous discovery approach where designers run lightweight usability tests every sprint rather than waiting for a dedicated research phase.
- Atlassian integrates UX work into Jira boards alongside engineering tasks, giving designers, researchers, and developers a shared sprint backlog.