Agile Project Assessment Template

---
title: "Agile Project Assessment Template"
methodology: "agile"
complexity: "starter"
process_group: "initiating"
industry: "universal"
role: "po"
tags: ["agile", "initiating", "stakeholder-management", "communication", "planning", "quality"]
version: "1.0.0"
owner: "mirichard"
updated: "2026-09-19"
estimated_completion_time: "15-30 minutes"
primary_principles: ["adaptability", "evidence-based-decisions"]
secondary_principles: ["stakeholder-engagement", "continuous-learning"]
principle_rationale: "Uses evidence and feedback to tailor an agile approach to project context."
---


# Agile Project Assessment Template

## When to Use

- When reviewing an established Agile team's delivery practices and improvement priorities.
- When iteration evidence, stakeholder feedback, and team observations can support a maturity discussion.

## When NOT to Use

- To rate a traditional project's phase gates; use the waterfall assessment.
- Do not report sample values, unsupported ratings, or missing data as verified performance. See [Metric without source](../../../docs/principles/anti-patterns.md#metric-source).

## Pairs Well With

- [Hybrid Project Assessment Template](../../../domains/delivery/project-assessment-suite/hybrid-project-assessment-template.md).
- [Project Health Assessment Template](../../../domains/measurement/project-assessment-suite/project-health-assessment-template.md).

Selection context: Delivery domain; universal methodology; starter complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../meta/architecture-research/800-801-context-assessment-model.md).

## Executive Summary
This template provides an assessment framework specifically designed for Agile projects and teams.

## Agile Assessment Overview
**Team/Project:** [Name]
**Methodology:** [Scrum/Kanban/SAFe/Other]
**Assessment Date:** [Date]
**Team Size:** [Number of team members]
**Sprint Duration:** [Length]

## Agile Practices Assessment

### 1. Scrum Events Effectiveness
**Event Assessment:**
- [ ] **Sprint Planning:** Quality and outcomes
- [ ] **Daily Scrum:** Effectiveness and value
- [ ] **Sprint Review:** Stakeholder engagement
- [ ] **Sprint Retrospective:** Continuous improvement

**Maturity Score:** [1-5 for each event]

### 2. Team Collaboration
**Collaboration Indicators:**
- [ ] Cross-functional team composition
- [ ] Self-organization capability
- [ ] Communication effectiveness
- [ ] Collective ownership mindset

### 3. Customer Collaboration
**Customer Engagement:**
- [ ] Product Owner involvement
- [ ] Stakeholder feedback incorporation
- [ ] User story quality
- [ ] Acceptance criteria clarity

### 4. Technical Practices
**Engineering Practices:**
- [ ] Test-driven development
- [ ] Continuous integration
- [ ] Code quality standards
- [ ] Technical debt management

## Agile Metrics Assessment
**Key Metrics:**
- Velocity trends
- Sprint goal achievement
- Customer satisfaction
- Team satisfaction
- Defect rates

## Improvement Recommendations
**Focus Areas:**
1. [High priority improvement]
2. [Medium priority improvement]
3. [Continuous improvement suggestions]

## Assessment method and evidence

Tailor the criteria to the project before scoring. This is a lightweight internal assessment, not a certification or formal appraisal. Mark inapplicable criteria N/A with a rationale; distinguish missing evidence from poor performance.

Use a locally agreed scale: 1 = absent/ad hoc; 2 = inconsistently applied; 3 = defined and routinely applied; 4 = measured and controlled; 5 = improved using measured outcomes. Record evidence for each rating. Do not average scores with N/A or unassessed items.

| Criterion | Rating / N/A / not assessed | Dated evidence and rationale | Gap / impact | Action / owner / due date | Completion evidence |
|---|---|---|---|---|---|
| [Criterion] | [Rating] | [Source and observation] | [Gap] | [Action / name / date] | [Observable acceptance condition] |

- **Assessment limitations:** [Sampling, unavailable information, assessor familiarity]
- **Stakeholder review:** [Reviewer / date / disputed findings]
- **Follow-up review:** [Date and accountable owner]

Related Resources:
- [Agile Scrum Framework](../methodology-frameworks/agile-scrum/)
- [Sprint Planning](../methodology-frameworks/agile-scrum/sprint-planning/)