Alpha

Purpose

Alpha is used to test possible solutions and the riskiest assumptions.

The goal is to learn which approach is most likely to work before building at scale.

Alpha Principles

During alpha, we:

• test ideas quickly

• prototype only what is necessary

• focus on risky assumptions

• avoid premature production build

• challenge existing ways of working

• learn from users and stakeholders

• decide what should move into beta

Alpha Activities

Typical alpha activities include:

• prototype design

• technical feasibility testing

• user journey testing

• architecture options

• integration experiments

• security risk exploration

• data-sharing feasibility

• operational impact assessment

• commercial model refinement

Alpha Outputs

Alpha should produce:

• tested prototype or prototypes

• evidence of user feedback

• technical feasibility assessment

• preferred solution option

• delivery risks

• beta backlog

• beta roadmap

• updated commercial assumptions

• recommendation to proceed, stop, or reshape

Exit Criteria

Alpha is complete when:

• key assumptions have been tested

• the preferred solution is justified by evidence

• major risks are visible

• beta scope is defined

• beta delivery approach is credible