TechSoft
Menu
Playbook menu: Stage 2: Design

Delivery Playbook · Lifecycle

Stage 2: Design

Define what will be built, how it will be built and how it will be accepted.

Goal: Define what will be built, how, and how it will be accepted.

Activities

  • Architecture and integration design, with recorded decisions
  • Prioritized backlog with acceptance criteria
  • Prototype and usability check where users are involved
  • Test strategy, release plan and AI-use plan

Artifacts

  • Architecture and ADRs
  • Backlog and roadmap
  • Prototypes and design specs
  • Test and release strategy
  • Security and data-handling plan

Exit criteria

Architecture, scope for the first release and acceptance criteria approved by customer and Tech Lead.

Who is involved

  • Customer Sponsor
  • Engagement Manager
  • Delivery Lead
  • Business Analyst · leads
  • UX/UI Designer · leads
  • Tech Lead / Architect · leads
  • Software Engineers
  • QA / Test Automation
  • DevOps / Platform
  • Security & Compliance
  • AI / Data Engineer
  • Support & Operations

A typical Design, step by step

  1. 1

    Shape the solution

    Turn the problem statement into options and choose the smallest solution that achieves the outcome.

  2. 2

    Architecture and integration design

    Define components, data model, integrations, hosting and non-functional requirements. Record key decisions as ADRs.

  3. 3

    Backlog and acceptance criteria

    Break the scope into stories that each deliver value on their own. Each has testable acceptance criteria.

  4. 4

    Prototype and test with users

    Where users are involved, make clickable prototypes and test them before building.

  5. 5

    Test, release and AI-use plan

    Agree how the work will be tested and released, and which AI tools may be used on which parts.

  6. 6

    Approval

    Customer and Tech Lead approve architecture, first-release scope and acceptance criteria.

01DiscoverProblem and baseline02DesignArchitecture and scope03BuildReviewed increments04VerifyGates and acceptance05OperateRun and improveMeasure outcomes, learn, and feed the next increment◆ = exit gate
Each stage ends with an exit gate agreed with the customer. What we learn in Operate feeds the next round of Discover.

Related