TechSoft
Playbook menu: Metrics and reporting

Delivery Playbook · 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.

Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027

We measure four things: how fast we deliver, how well the software works, whether AI is really helping, and whether the business result improved. These are the measures we propose. They are definitions, not results.

Delivery

How quickly useful software reaches users.

Lead time for changes
Time from a change being started to it running in production
Time to first usable release
Time from kickoff to the first release real users can use
Deployment frequency
How often we release to production

Quality and reliability

Whether what we ship works and stays working.

Escaped defects
Defects found in production that testing should have caught
Change failure rate
Share of releases that cause a failure or need a fix or rollback
Time to restore service
How long it takes to recover from an incident
Security findings and remediation
Findings raised, and how long they take to close

AI effectiveness

Whether AI is really helping, not just producing more code.

Time saved on selected tasks
Compared with the same kind of task before AI, on agreed examples
AI-assisted changes accepted after review
Share of AI-assisted changes that pass review
Rework from AI-generated changes
Fixes and rewrites needed after AI-assisted work
Verification and review effort
Time people spend checking AI output

Business outcomes

Whether the software moved something the client cares about.

Time to market
Time from idea to clients using it
Feature adoption
How many people actually use what we shipped
Operating cost
Cost to run and support the software
Client-defined return on investment
Measured against the client's own definition of value

From engineering measures to business outcomes

Delivery

Faster, smaller releases

Quality and reliability

Fewer failures, faster recovery

AI effectiveness

Time saved, minus the checking it needs

Business outcomes

Time to market, adoption, cost, your own ROI

Engineering measures only matter when they move an outcome you care about. That is why each engagement starts by agreeing the outcome and its baseline.

How we keep the numbers honest

  • Every metric has a baseline recorded in Discover, so we can compare against where you started.
  • Every metric has a measurement period and one agreed definition, so numbers mean the same thing month to month.
  • The measures on this page are the ones we propose. Actual results are reported per engagement. We do not publish targets or results here that we cannot back up.
  • We do not use lines of code or the amount of AI-generated code as measures of productivity.

Reporting

ReportFrequencyContentsOwner
Sprint reportEach sprintGoal, what was finished, demo notes, carry-overDelivery Manager
Weekly statusWeeklyProgress, risks, decisions needed, next stepsDelivery Manager
Monthly reviewMonthlyOutcomes vs baseline, engineering health, budget, roadmapDelivery Manager
Release notesEach releaseWhat changed, known issues, rollback planDelivery Manager, QA

Related