Your web browser is out of date
Your web browser (the software you use to access the internet) is out of date. You need to update it or use a different web browser to ensure you can complete this form.
How we work
Overview
We use Kanban to manage our software development lifecycle. It gives stakeholders a clear view of progress and lets contributors move work through a shared process with minimal friction.
Kanban sits alongside Lean thinking — they tackle different aspects of delivery and complement each other. Both approaches grew out of Toyota’s work on improving production flow.
Our working model
Work starts as a user story on the backlog, moves across the Kanban board, and is released through continuous integration and delivery. Every two weeks we hold a retrospective so the process itself keeps improving.
Process pages
- Agile and Kanban — board columns, backlog vs to do, and how work flows
- Gitflow and releases — branching, pull requests, CI, and release approval
- User stories — how we write and work with stories
- Definition of done — criteria for a story to be complete and releasable
Retrospectives
Every two weeks we meet as a team so each member can discuss:
- What worked well for us?
- What did not work well for us?
- What actions can we take to improve our process going forward?
Members can log items during the two-week cycle, or raise them in the retrospective. These meetings drive our working style and capture lessons learned. Principles for writing stories, in particular, often account for a large share of what we review and adapt.
Related guidance
How we build is inseparable from how we keep services safe and usable:
- Secure by design — security controls embedded in design, build, and maintenance
- Accessibility — progressive enhancement, WCAG, and sustainability (Design System)
Contacts
- Christian King -- Development Team Lead
Published 21 September 2026
Last updated 21 September 2026