Answers common questions about integrating design and UX work into Scrum Sprints, clarifying why dedicated Design Sprints aren’t needed and how to align with Scrum principles.
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?
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.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
CR2
Milliman
Xceptor - Process and Data Automation
YearUp.org
Boeing
Brandes Investment Partners L.P.
Illumina
Kongsberg Maritime
Genus Breeding Ltd
Akaditi
Flowmaster (a Mentor Graphics Company)
Alignment Healthcare
MacDonald Humfrey (Automation) Ltd.
Slaughter and May
Qualco
DFDS
Big Data for Humans
ProgramUtvikling
New Hampshire Supreme Court
Nottingham County Council
Washington Department of Transport
Royal Air Force
Department of Work and Pensions (UK)
Washington Department of Enterprise Services
Teleplan
SuperControl
MacDonald Humfrey (Automation) Ltd.
Genus Breeding Ltd
Hubtel Ghana
Sage
