Our process
A typical product sprint runs over four to eight weeks. We agree the scope and timing first, then review the product together as it develops.
Understand the problem.
Before the build · We learn who the product is for, how the work happens today and what a useful result would look like. We check the important assumptions and decide whether there is a sensible first scope.
- The user problem and desired outcome
- Constraints, risks and open questions
- A decision on the next step
Set the scope. Make it tangible.
Weeks 1–2 · We agree the core journey, priorities and acceptance criteria. Design and the first working build make the plan concrete. You can react to the product before too much is built around an assumption.
- Agreed scope and release plan
- Core screens and user journey
- First working version to review
Build, test and hand over.
Weeks 3–8 · We develop in small releases, review progress together and test the important journeys. Launch includes access, operating instructions and a clear handover. Further development is a separate, explicit decision.
- Regular working releases
- Checks against the agreed acceptance criteria
- Deployment, documentation and handover
Have a problem in mind?
Tell us what you want to change. We’ll work out the next step together.