Delivery Playbook · Roles
Project leadership and responsibilities
The Client Sponsor, our Delivery Manager and our CTO.
Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027
These roles set direction, look after the relationship and keep delivery predictable. The Client Sponsor is the person on your side who can make business decisions and is accountable for the outcome. This might be a founder, an owner, a department head or a product director. They may name a product owner to work with the team day to day. On our side, the Delivery Manager runs the engagement and the team's rhythm. The CTO looks after technical direction, security, compliance, AI and data.
Client Sponsor
ClientThe client's decision-maker. Owns the business outcome, priorities and acceptance.
Owns
- Business goals and success measures
- Backlog priority and scope trade-offs
- Acceptance of delivered increments and release approval
- Access to users, data and systems
Day to day
- Joins planning, review and monthly steering meetings
- Answers questions within the agreed response time
- Names a product owner and technical contacts for day-to-day work, if needed
Use of AI: Agrees which AI tools may be used on their code and data, and under what conditions.
Works with: Receives demos, reports and release notes; approves releases.
Delivery Manager
TechSoftOwns the client relationship and keeps delivery predictable: the plan, the flow of work, the risks and the rhythm.
Owns
- Engagement scope, terms and change control
- Sprint and release plan, flow metrics and delivery forecast
- Client communication, steering reviews and the risk register
- Impediment removal and team working agreements
Day to day
- Runs kickoff, planning, daily sync, review and retrospective
- Publishes the weekly status and the monthly review
- Tracks risks, dependencies and decisions, and escalates early
- Keeps the board and the definitions of ready and done honest
- Collects client feedback and acts on it
Use of AI: Tracks the effect of AI on speed and quality, and makes sure the agreed AI-use policy is followed and visible to the client.
Works with: Works daily with the Tech Lead and the whole team; escalates to the TechSoft CTO and the Client Sponsor.
CTO (Security, Compliance, AI & Data)
TechSoftOwns technology direction across engagements, and keeps client data, systems and AI use safe and auditable.
Owns
- Security and compliance requirements and review
- AI-use policy: approved tools and data-handling rules
- Design of AI and data features, and how they are evaluated and monitored
- Dependency and secrets hygiene
- Evidence supporting client compliance work
Day to day
- Threat-models critical features and reviews data flows and third-party services
- Decides with the Tech Lead where AI fits and where ordinary automation is better
- Sets permissions, approvals and audit trails for AI features
- Reviews evaluation results and production behavior of AI features
- Advises on regulated-data constraints and is the escalation point for technical risk
Use of AI: Defines which tools are approved and which data may reach them. Responsible for how the AI features delivered to the client behave.
Works with: Advises the Tech Lead and Delivery Manager; reports risks to the Client Sponsor.
Where they are involved
| Discover | Design | Build with AI | Verify | Operate & improve | |
|---|---|---|---|---|---|
| Client Sponsor | ••• | •• | • | •• | •• |
| Delivery Manager | ••• | •• | ••• | •• | ••• |
| CTO | • | •• | ••• | ••• | •• |
Related
Working agreements
Cadence and meetings
The rhythm of an engagement: what happens daily, weekly, per sprint and monthly.
Governance
Escalation and risk
How problems move up quickly, and how risks are managed before they become problems.
Governance
Metrics and reporting
What we measure across delivery, quality, AI and business outcomes, how we report it, and how the numbers lead to decisions.
