> For the complete documentation index, see [llms.txt](https://framework.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.aic.io/agile-delivery-playbook/delivery-system/measuring-progress-and-performance.md).

# Measuring Progress and Performance

### Overview

Agile progress is measured through evidence, not optimism. We use a balanced view of progress that includes delivery output, user value, quality, risk, service health and commercial position.

### Delivery Progress Measures

Delivery progress may include:

* backlog items completed
* sprint goal achieved
* milestones completed
* deliverables accepted
* blockers removed
* risks reduced
* decisions made
* releases completed
* defects resolved
* evidence produced

### User and Service Measures

User and service measures may include:

* task completion rate
* user satisfaction
* support tickets
* call volume
* abandonment rate
* time to complete task
* accessibility findings
* research findings
* service analytics
* feedback themes

### Technical Measures

Technical measures may include:

* test pass rate
* defect trends
* deployment frequency
* failed deployment rate
* recovery time
* performance results
* security vulnerabilities
* dependency health
* code review completion
* technical debt items

### Commercial Measures

Commercial measures may include:

* milestone status
* accepted deliverables
* invoice readiness
* change request status
* scope variance
* customer dependency performance
* supplier performance
* remaining budget

### Risk and Assurance Measures

Risk and assurance measures may include:

* open high risks
* open high issues
* overdue decisions
* unresolved dependencies
* security findings
* data protection actions
* accessibility actions
* audit evidence gaps

### Status Reporting

Status should be honest and evidence-based.

### <mark style="color:$success;">Green</mark>

<mark style="color:$success;">Delivery is on track. No material intervention is required.</mark>

### <mark style="color:$warning;">Amber</mark>

<mark style="color:$warning;">Delivery is at risk. Management action, customer decision or scope trade-off may be required.</mark>

### <mark style="color:$danger;">Red</mark>

<mark style="color:$danger;">Delivery is materially off track. Immediate escalation is required.</mark>

### Good Reporting Questions

A good report answers:

* What has changed?
* What has been completed?
* What value or evidence was produced?
* What is planned next?
* What is blocked?
* What decisions are needed?
* What risks or issues require attention?
* Is scope still aligned to the Statement of Work?
* Are milestones and acceptance criteria still achievable?

### Avoiding Vanity Metrics

Do not rely only on measures that look positive but do not explain real progress.

Weak measures include:

* number of meetings held
* number of documents produced
* percentage complete without evidence
* effort spent without outcome
* activity without user or customer value

### Evidence Standard

Where a measure is used for governance, acceptance or payment, it should be supported by evidence.