In Scrum, we don’t do UX separately

TL;DR; UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed.

Published on 12 June 2025

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/H1avNshoB3O

In Scrum, we don’t do UX separately. We don’t have a “UX Sprint.” UX is part of the product. That means UX work is either:

Needed to meet the Sprint Goal—so it’s done during the Sprint.
Needed for future work—so it’s done as part of ongoing Product Backlog Refinement.

It’s that simple.

If you’re off doing speculative design in a vacuum, disconnected from the team, you’re not doing Scrum. You’re delaying learning and undermining flow. UX belongs in the real world, integrated into the delivery of value, not staged like a phase from a project plan.

Design as you go. Validate early. Iterate continuously.

Still running “design sprints”? Maybe it’s time to rethink what “done” really means for your team.

Also published on: LinkedIn

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.