Delivery process
From context to a controlled release.
The process is staged so price, functionality and responsibility can be reviewed before irreversible decisions are made.
Representative visual03 / processSix stages
Work advances through evidence.
Exact stage content is adapted to each project, while the decision sequence remains visible.
Starting context
Goal, users, current situation and intended business outcome.
→Product boundaries
Features, data, integrations, exceptions and acceptance criteria.
→Technical model
Interface, data structure, access and delivery sequence.
→Working releases
Functional increments are demonstrated and reviewed regularly.
→Stabilisation
Error states, core journeys, performance and access are checked.
→Handover and continuation
Release, documentation and a clear next-improvement list.
→Stage outputs
Not just discussion — a working artefact.
Scope map
Users, journeys, functions, integrations and exceptions.
Acceptance criteria
A testable description of what a particular release does.
Decision record
Material assumptions and changes affecting price or timing.
Handover set
Access, configuration and the continuation backlog.
Starting point
Boundaries come first.
Describe the current situation, intended users and required outcome. The initial response will establish whether the concept fits the indicative €1,000–€2,000 working range.