Delivery Playbook · Start here
Principles
Our four values, and the six working rules that put them into practice.
Owner: Leadership Team · Last reviewed: · Next review: 28 April 2027
Four values guide how we work: Kindness, Sustainability, One-Team and Excellence. They are not slogans. Each one shows up in how we plan, build, review and report. Below you will find each value, what it looks like in delivery, and the six working rules that put them into practice.
Our four values
#Kindness
We treat people the way we want to be treated. We are honest and open, we respect one another, and we support and encourage each other, in the team and with our clients. In delivery: We listen before we propose, in interviews and workshops; Retrospectives look at how we work, not who to blame; We share bad news and risks early, with options attached; Code review is about the code, and it is always polite.
#Sustainability
We think long term. We look after our health, keep learning and growing, and share what we know with our team and the wider community. In delivery: A steady one-week rhythm, so the pace can continue; Every change is understood by an engineer before it ships; Runbooks and documentation are part of the work; Small, reversible releases instead of big risky ones.
#One-Team
We share goals and succeed together. Everyone takes ownership of their work, looks for practical ways to move forward, and celebrates results as a team, including our clients. In delivery: The client's product owner takes part in planning and review; Design, QA and DevOps sit in the team from day one; One backlog and one board that everyone can see; Every activity has one role accountable for it.
#Excellence
We care about quality and stand behind our work. We hold ourselves accountable and aim to get a little better every day. In delivery: A clear definition of done, with no "almost done"; Four quality gates between an idea and production; Tests, security checks and review on every change; Results measured against a baseline recorded at the start.
Six working rules
A playbook only helps if people follow it when it is inconvenient. When two good options conflict, these rules help the team decide.
1. Outcomes before output · #Excellence
Before we write code, we agree with you what success looks like and how we will measure it against a baseline. A feature that ships but does not change the outcome has not succeeded.
2. One team with the client · #One-Team
Everyone knows their role, on the client side and ours. The client's product owner is part of the team from the start, not a reviewer at the end.
3. Small increments, visible progress · #Sustainability
We release often and show working software. We prefer many small steps that are easy to reverse over one large, risky one.
4. AI speeds us up, people own the result · #Sustainability
AI is part of how we work. A named engineer understands, reviews and owns every change.
5. Quality is built in · #Excellence
Tests, security checks and review happen with every change, not in a phase at the end.
6. Honest reporting · #Kindness
We share risks, trade-offs and open issues early, even when the news is uncomfortable.
How the rules show up day to day
| Working rule | In practice | Where to read more |
|---|---|---|
| Outcomes before output | We record success measures and a baseline in Discover, then review them monthly | Discover · Metrics & reporting |
| One team with the client | The client product owner joins planning and review; one shared backlog | Cadence & meetings · Decision rights |
| Small increments | Sprint demos; releases behind rollback plans | Build · Quality gates |
| AI speeds us up, people own the result | AI-use policy; mandatory human review | AI-assisted engineering |
| Quality is built in | Definition of done; automated gates in the pipeline | Definition of ready & done · Quality gates |
| Honest reporting | Weekly status with risks, and a clear escalation path | Escalation & risk |
Related
Start here
How the team is organized
The client and TechSoft roles in an engagement, and how they work together.
Quality & AI
AI engineering
How AI supports the whole engineering workflow, who is responsible for what, and the rules that keep it safe.
Quality & AI
Quality gates
Four gates a change passes between idea and production, and what each one checks.
