Solution Design Sprint

For a team that has to make a concrete architecture decision and is caught between competing options and constraints.

Length
Two weeks
Scope
One bounded design question
Format
Stakeholder workshops and independent design time
Options compared
Up to three
Ask about a Design Sprint

Who it is for

A team that needs to make a concrete architecture decision, such as how to modernize application delivery or secure access, and has competing options and constraints.

The engagement

Two weeks for one bounded design question, combining stakeholder workshops with independent design time.

Included

  • Requirements and constraints, with the assumptions stated.
  • A review of up to three feasible options.
  • One recommended high-level architecture.
  • A decision and risk register.
  • An implementation roadmap, and a readout.

Not included unless specified

  • A detailed bill of materials.
  • Vendor procurement.
  • Low-level engineering.
  • Production implementation.

What you provide

  • A sponsor who owns the decision.
  • The people who hold the requirements and the constraints.
  • The designs, contracts and proposals relevant to the question.
  • A reviewer for the recommendation.

How it is accepted

The sprint is accepted when the requirements, options, rationale and decisions are traceable to each other, and the recommendation has been read out to the people who decide.

If it is useful, what comes next

An implementation-readiness phase, or ongoing design-to-delivery advice through a Modernization Partnership.