Home / UX/UI Design

🎨 Phase 3: UX/UI Design

Design sprint running parallel to development sprints

On This Page

Design Sprint Overview

The design sprint runs in parallel with the development sprint, staying one sprint ahead. This ensures developers always have finalized designs when Sprint Planning begins.

Tool: All designs are created and maintained in Figma.
Not every change needs new designs. Bug fixes, backend changes, and minor UI tweaks can reference existing patterns.
Requirements
→
Discovery
→
Wireframes
→
High-Fidelity
→
Design Handoff

Two-Week Design Cycle

Week 1: Discovery & Wireframes

  • UX reviews requirements with PO
  • User journey mapping
  • Low-fidelity wireframes
  • Flow diagrams and user flows
  • Initial stakeholder feedback

Week 2: High-Fidelity Designs

  • Visual design completion
  • Prototype creation (if needed)
  • Component specifications
  • Design review with PO and stakeholders
  • Design handoff preparation

Design Handoff Criteria

Before a design is considered "Ready for Development", it must include:

Incomplete Designs: Designs missing any required states or specifications should not proceed to development. Flag these during design review.

Design Review Sessions

Aspect Details
Frequency Weekly
Duration 1 hour
Attendees Product Owner, Functional Lead, Technical Lead, UX/UI Designers

Review Agenda

  1. Present completed designs from current week
  2. Gather feedback from stakeholders
  3. Validate against business requirements
  4. Technical Lead reviews for feasibility
  5. Identify any blockers or concerns
  6. Approve for handoff or request revisions

Design-Development Cadence

Key Rule: Designs must be completed at least one sprint ahead of development. This ensures the Dev team has finalized, approved designs at Sprint Planning.
Sprint N Design Team Dev Team
Week 1-2 Designing Sprint N+1 features Building Sprint N features
Week 2 End Handoff Sprint N+1 designs Sprint N Review/Retro
Week 3 Starting Sprint N+2 designs Sprint N+1 Planning (with designs ready)

Next Phase

Once designs are complete, the Product Owner and Stakeholders create the Product Requirements Document (PRD) which becomes the foundation for development.