AGILE DESIGN

Sprints

OVERVIEW

Forest Before Trees

Agile delivery often fragments design task before designers ever see the full picture. Requirements are broken into tickets, handed off in pieces, and stripped of the broader context that gives product experiences coherence. As a result, designers become order takers instead of strategic partners. I set out to create a continuous design delivery model that helped my team understand the whole experience first, then iterate on the details in step with agile development.

OVERVIEW

Forest Before Trees

MY APPROACH

Agile by Design

I approached continuous design delivery as a cross-functional systems problem. By studying agile methods, observing product discovery, speaking with engineers, and comparing how other teams handled the same challenge, I identified the breakdowns that kept design from working smoothly inside agile delivery.

ACTIVITY BREAKDOWN

TRAINING AND DEVELOPMENT

40%

BUSINESS PROCESS ANALYSIS

30%

INTERVIEWS

20%

TEAM OBSERVATION

10%

UNDERSTAND

Conversations with Engineering

I met with engineers to identify gaps in our design documentation and understand what makes a ticket ready for development. This clarified missing information for estimation and planning, improving how design work was prepared for handoff.

UNDERSTAND

Observed Product Discovery Practices

I observed product owners as they worked with business stakeholders to gather requirements. This clarified how product management and design strategy complement each other, aligning big-picture thinking with detailed functional decision-making.

SERVICE MAPPING

Current State Analysis

I spoke with design peers to document how Agile design sprints were working in practice. Many had abandoned them in favor of waterfall approaches, revealing common pain points and reinforcing the need for a more adaptable, modern design workflow.

EXPLORE

Agile Development Training

I expanded my understanding of Agile methodologies through targeted learning and hands-on experience, focusing on sprint structure and key ceremonies. This helped me better support the team and ensure design work aligned with how Agile delivery actually operates.

UNDERSTAND

Conversations with Engineering

UNDERSTAND

Observed Product Discovery Practices

SERVICE MAPPING

Current State Analysis

EXPLORE

Agile Development Training

UNDERSTAND

Conversations with Engineering

UNDERSTAND

Observed Product Discovery Practices

SERVICE MAPPING

Current State Analysis

EXPLORE

Agile Development Training

UNDERSTAND

Conversations with Engineering

UNDERSTAND

Observed Product Discovery Practices

SERVICE MAPPING

Current State Analysis

EXPLORE

Agile Development Training

Problems to Solve

This work revealed four issues the new design delivery process had to address

This work revealed four issues the new design
delivery process had to address

01 / REQUIREMENTS

Missing Context

Requirements often arrived vague or incomplete, leaving out the user needs, business goals, and broader product context needed to make sound design decisions.

01 / REQUIREMENTS

Missing Context

Requirements often arrived vague or incomplete, leaving out the user needs, business goals, and broader product context needed to make sound design decisions.

O2 / TEAMWORK

Siloed Teams

Designers and engineers were not collaborating early enough, making it harder to surface constraints, align on implementation, and shape a coherent experience together.

O2 / TEAMWORK

Siloed Teams

Designers and engineers were not collaborating early enough, making it harder to surface constraints, align on implementation, and shape a coherent experience together.

03 / FEEDBACK

Rushed Revisions

Feedback often landed too close to development handoff, leaving little time to revise and strengthen the work before engineering needed finalized designs.

03 / FEEDBACK

Rushed Revisions

Feedback often landed too close to development handoff, leaving little time to revise and strengthen the work before engineering needed finalized designs.

04 / PROJECT SETUP

Failure to Launch

Teams often entered design work without the foundational setup in place—from file architecture and style guidance to the first reusable components needed to work efficiently.

04 / PROJECT SETUP

Failure to Launch

Teams often entered design work without the foundational setup in place—from file architecture and style guidance to the first reusable components needed to work efficiently.

The Solution

Strong user experiences depend on more than creative talent—they depend on context, collaboration, and timing. To make design sprints work inside agile delivery, I introduced two key ingredients: richer design stories that gave designers the full picture, and a clearer sprint cadence that created space for exploration, review, and approval before development began.

KEY DELIVERABLES

PROCESS DOCUMENTATION

•

TRAINING MATERIAL

•

TOOLS AND TEMPLATES

The Solution

KEY DELIVERABLES

PROCESS DOCUMENTATION

TRAINING MATERIAL

TOOLS AND TEMPLATES

The Solution

KEY DELIVERABLES

PROCESS DOCUMENTATION

•

TRAINING MATERIAL

•

TOOLS AND TEMPLATES

Introducing Design Stories

I evolved the traditional design brief into a design story—a build-ready blueprint that aligns user context, task goals, interaction needs, design system guidance, and technical constraints in a single working document. It gave designers the clarity needed to design core workflows without ambiguity, while ensuring product and engineering were aligned before UI work began. This reduced rework and created a shared understanding of what needed to be built and why.

TEMPLATE

Design Story: [Page or Feature Name]

This document provides the context, requirements, and technical information needed to design and build the [page or feature name].

Target User and Context of Use

User Persona

Who are they?

Short description of the primary persona for this feature

Key Needs

What are the goals and needs related to this task

Pain Points

What challenges or frustrations might they have?

Context of Use

Where are they? What device are they using? Any relevant constraints?

Task Overview

What is the user trying to accomplish?

Describe the primary task the user is trying to complete using the feature

Step in the workflow

How does this feature fit into the larger task workflow? What happens before and after this step?

Design Requirements

Design Story (1 of 4)

As a [type of user], I want to [action] so that [benefit]

Description

e.g., Search for dentists by location, name, or specialty

Acceptance / Success Criteria

• Search returns relevant results
• Results update as I type
• I can refine my search easily

Primary User Actions

What the user needs to see, do, compare, or decide on this page/feature

• See a search field with autosuggest and clear input • View a list or map of matching dentists • Filter and sort results • Compare options and select a dentist • Proceed to dentist profile or booking

Design References

Brand / Style Guidelines

+ Link to brand guidelines or visual direction

Component Library

+ Link to relevant components

Existing Patterns / Examples

+ Link to pattern library

Other Resources

Technical Notes

Tech Stack

e.g., Frontend: React / Next.js Backend: Node.js Database: PostgreSQL

Library / Services

e.g. Algolia (search), Maps API

Existing Patterns / Examples

e.g., Performance, Accessibility (WCAG 2.2 AA). SEO

Dependencies

e.g., APIs, services, other teams or upstream systems

TEMPLATE

Design Story: [Page or Feature Name]

This document provides the context, requirements, and technical information needed to design and build the [page or feature name].

Target User and Context of Use

User Persona

Who are they?

Short description of the primary persona for this feature

Key Needs

What are the goals and needs related to this task

Pain Points

What challenges or frustrations might they have?

Context of Use

Where are they? What device are they using? Any relevant constraints?

Task Overview

What is the user trying to accomplish?

Describe the primary task the user is trying to complete using the feature

Step in the workflow

How does this feature fit into the larger task workflow? What happens before and after this step?

Design Requirements

Design Story (1 of 4)

As a [type of user], I want to [action] so that [benefit]

Description

e.g., Search for dentists by location, name, or specialty

Acceptance / Success Criteria

• Search returns relevant results
• Results update as I type
• I can refine my search easily

Primary User Actions

What the user needs to see, do, compare, or decide on this page/feature

Design References

Brand / Style Guidelines

+ Link to brand guidelines or visual direction

Component Library

+ Link to relevant components

Existing Patterns / Examples

+ Link to pattern library

Other Resources

Technical Notes

Tech Stack

e.g., Frontend: React / Next.js Backend: Node.js Database: PostgreSQL

Library / Services

e.g. Algolia (search), Maps API

Existing Patterns / Examples

e.g., Performance, Accessibility (WCAG 2.2 AA). SEO

Dependencies

e.g., APIs, services, other teams or upstream systems

TEMPLATE

Design Story: [Page or Feature Name]

This document provides the context, requirements, and technical information needed to design and build the [page or feature name].

Target User and Context of Use

User Persona

Who are they?

Short description of the primary persona for this feature

Key Needs

What are the goals and needs related to this task

Pain Points

What challenges or frustrations might they have?

Context of Use

Where are they? What device are they using? Any relevant constraints?

Task Overview

What is the user trying to accomplish?

Describe the primary task the user is trying to complete using the feature

Step in the workflow

How does this feature fit into the larger task workflow? What happens before and after this step?

Design Requirements

Design Story (1 of 4)

As a [type of user], I want to [action] so that [benefit]

Description

e.g., Search for dentists by location, name, or specialty

Acceptance / Success Criteria

• Search returns relevant results
• Results update as I type
• I can refine my search easily

Primary User Actions

What the user needs to see, do, compare, or decide on this page/feature

Design References

Brand / Style Guidelines

+ Link to brand guidelines or visual direction

Component Library

+ Link to relevant components

Existing Patterns / Examples

+ Link to pattern library

Other Resources

Technical Notes

Tech Stack

e.g., Frontend: React / Next.js Backend: Node.js Database: PostgreSQL

Library / Services

e.g. Algolia (search), Maps API

Existing Patterns / Examples

e.g., Performance, Accessibility (WCAG 2.2 AA). SEO

Dependencies

e.g., APIs, services, other teams or upstream systems

PROCESS DOCUMENTATION

The Design Sprint

I created and implemented a two-week design sprint that guides teams from alignment and functional design through visual and interaction refinement, culminating in review and delivery.

Week One:

Explore and Design

MONDAY

KICKOFF

At the sprint kickoff, PMs and Design Strategists align with designers on open questions, goals, constraints, key decisions, and success criteria before design work begins.

MONDAY - WEDNESDAY

FUNCTIONAL DESIGN

Initial wireframes focus on workflows, tasks, and core functionality, helping the team explore, validate, and clarify what users need to see, do, or complete.

THURSDAY

DESIGN REVIEW (1 OF 3)

Early reviews of mid-fidelity wireframes clarify what users can see and do, validate requirements, and surface ideas before high-fidelity design begins.

THURSDAY - FRIDAY

EXPERIENCE DESIGN

Wireframes evolve into high-fidelity comps, refining usability, visual quality, and consistency with brand standards and design system patterns before final interaction polish.

Week Two:

Refine and Deliver

MONDAY - TUESDAY

EXPERIENCE DESIGN

Wireframes evolve into high-fidelity comps, refining usability, visual quality, and consistency with brand standards and design system patterns before final interaction polish.

TUESDAY

DESIGN REVIEW (2 OF 3)

Mid-sprint UI reviews use visual comps to evaluate how the experience works, focusing on usability, visual quality, and consistency with brand and system patterns.

TUESDAY - THURSDAY

INTERACTION DESIGN

High-fidelity comps become interactive prototypes that define how the experience behaves across workflows, states, transitions, and microinteractions.

FRIDAY

FINAL DOCUMENTATION

Final edits are completed, Development stories areupdated with design links, documentation is refreshed, and finalized patterns are added to the shared library.

Week One:

Explore and Design

MONDAY

KICKOFF

At the sprint kickoff, PMs and Design Strategists align with designers on open questions, goals, constraints, key decisions, and success criteria before design work begins.

MON

TUE

WED

THU

FRI

PROCESS DOCUMENTATION

Variations on a Sprint

I created a set of focused sprint types to support different phases of product development, from alignment and discovery to testing, refinement, and support. Sprints range from one to three weeks, enabling predictable planning and consistent delivery.

DISCOVERY SPRINT

Explores and validates new ideas through structured discovery, moving from problem definition to rapid prototyping and user testing to inform direction

Define problems and opportunities

Explore and select concepts

Prototype and test ideas

DISCOVERY SPRINT

Explores and validates new ideas through structured discovery, moving from problem definition to rapid prototyping and user testing to inform direction

Define problems and opportunities

Explore and select concepts

Prototype and test ideas

SPRINT ZERO

Aligns teams on goals, scope, and direction while reviewing design stories, planning upcoming work, and establishing the foundation for design execution.

Review design requirements

Define art direction and patterns

Build initial design library

SPRINT ZERO

Aligns teams on goals, scope, and direction while reviewing design stories, planning upcoming work, and establishing the foundation for design execution.

Review design requirements

Define art direction and patterns

Build initial design library

USABILITY TESTING SPRINT

Test designs with users to evaluate usability, analyze findings, explore improvements, and define clear next steps for design refinement and delivery.

Conduct usability testing

Analyze findings and issues

Define improvements and next steps

USABILITY TESTING SPRINT

Test designs with users to evaluate usability, analyze findings, explore improvements, and define clear next steps for design refinement and delivery.

Conduct usability testing

Analyze findings and issues

Define improvements and next steps

BACKLOG SPRINT

Addresses smaller requests and break/fix work by prioritizing the backlog, reviewing updates, and maintaining consistency across design systems

Prioritize backlog items

Review and approve updates

Update system and documentation

BACKLOG SPRINT

Addresses smaller requests and break/fix work by prioritizing the backlog, reviewing updates, and maintaining consistency across design systems

Prioritize backlog items

Review and approve updates

Update system and documentation

Lessons Learned

Continuous design delivery taught me that agile does not have to reduce design to a series of disconnected tickets. The problem was not the sprint model itself, but the lack of shared context, early collaboration, and preparation around the work entering the sprint. By reframing the design brief as a richer design story, I helped teams connect user needs, business goals, technical constraints, and interaction requirements before design work began. That shift gave designers more room to think strategically while giving product and engineering a clearer foundation for planning and implementation. The larger lesson was that design quality depends as much on cadence as craft. When feedback arrives too late or requirements are too thin, even strong designers are forced into reactive work. Creating a predictable sprint structure, clearer story inputs, and focused sprint types gave the team a better way to balance exploration with delivery. It helped design move at the speed of agile without losing the big-picture thinking that makes product experiences feel coherent, usable, and intentional.