Design Sprints in Scrum: Common Questions and Practical Insights

TL;DR; There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it.

Published on 4 June 2025

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/8mcd8y-jiFX

I’m still surprised how often I get asked about “Design Sprints” in Scrum. Let’s be clear—there are no special Sprints. No Sprint 0. No release Sprint. No hardening Sprint. And definitely no Design Sprint.

Scrum is a social technology for solving complex problems. Trying to segment Sprints by function (design, test, build) reflects a Taylorist approach rooted in the Industrial Revolution, not the realities of modern product development.

If your UX work is critical to delivering the Sprint Goal, then it belongs in the Sprint. If it’s about preparing for the future, then it’s part of Refinement. But none of it needs a dedicated, isolated timebox.

The goal is high-quality working software, not siloed ceremonies.

How are you integrating UX, design, and architecture into your Sprint without breaking the flow?

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.