Home / Build & release
Small steps, shown often.
How code moves from an idea on a card to something your users rely on, and how we keep that journey calm.
the cycle
Two-week rhythm.
Development runs in short cycles. At the end of each one you see working software in a shared test environment and we agree the next priorities together.
Start of cycle
- Agree a goal written as a user outcome
- Pick the smallest set of changes that serve it
- Flag anything we are unsure about
End of cycle
- Demonstration in a real browser
- Short written summary and release notes
- Decision: release, hold or change course
From card to customer.
Written as a need
Each piece of work starts as a short description of what a person needs to do and how we will know it works. Acceptance criteria are written before code.
Built and tested
Code is written with automated tests for the important behaviour. Accessibility checks and basic security checks run on every change.
Reviewed
Another developer reviews every change before it is merged. Reviews look for clarity as well as correctness.
Staged
Merged work appears in a test environment you can open at any time. Nothing reaches users without passing through here.
Released
Releases are planned for working hours, with a rollback step agreed in advance. Larger changes can go to a small group of users first.
Watched
After release we check errors and the agreed success measure. Results feed straight into the next cycle's priorities.
The handover box.
Whether we continue working together or not, a product should never depend on one person's memory. Each handover includes:
- Repository access under your organisation's account
- Run-book: how to deploy, roll back and restore
- Decision log explaining the significant choices
- Environment list: what runs where and who holds access
- Known issues, written down rather than remembered
- A walk-through session for your team or your next supplier