The practice

From the first meeting to handover, in five steps.

Short scoping, a demo before the build, rapid delivery on a tested pipeline, and as many rounds of your feedback as it takes. A sixth step — staying on for the long term — is there for the products that need it.

A meeting, or a few

01 · Meet

A meeting, or a few

We do not open with a discovery programme. A meeting — sometimes a few — is usually enough to establish what the product has to do, who it is for, and what would count as finished. Anything still unclear goes on the list to settle at the demo rather than holding the project up.

Deliverable — an agreed scope, in writing

A demo that shows what we understood

02 · Demo

A demo that shows what we understood

Rather than hand back a specification for you to imagine, we build a demo that shows what we understood and put it in front of you. You mark it up, we correct it, and the build does not start in earnest until you agree it is right.

Deliverable — a working demo, and your notes on it

Rapid build, tested and shipped

03 · Build

Rapid build, tested and shipped

The build moves fast because deployment is automated — a short CI/CD workflow puts each change in front of you without ceremony. Testing is not what gets cut for it: before a release goes out it goes through a comprehensive session, a good deal of it by hand, because that is what actually finds the things that matter.

Deliverable — the working product, tested and deployed

Your feedback, for as many rounds as it takes

04 · Iterate

Your feedback, for as many rounds as it takes

Once it is in your hands the useful feedback starts, and it rarely arrives all at once. We keep iterating for as many rounds as it takes — the count is not capped, and asking for another pass is expected rather than an imposition. Automated tests run on every update through the iteration, so a change made for this round does not quietly break something that worked in the last.

Deliverable — a release for every round of feedback

Complete, and handed over in full

05 · Handover

Complete, and handed over in full

How long that takes depends on the product. When the iterations stop earning their place the work is complete, and the product, its code and everything needed to run it are handed over. The measure is simple: everyone is satisfied with what they got.

Deliverable — full handover of the product and its code

A long-term arrangement, where a product needs one

06 · Partner

A long-term arrangement, where a product needs one

Some products are finished at handover. Others keep moving, and for those we stay on: continued development, maintenance and accountability for as long as the product warrants it. It is an option, not a condition of working together.

Optional — an ongoing arrangement, for the products that call for it