§1 Principles of Assessment
Evaluating a project team effectively requires separating raw technical outputs from the behavioural inputs that produced them. This document standardises that separation.
This KEVOS® Team Performance Assessment template is designed for end-of-phase or end-of-project closeouts. It explicitly partitions a team's review into three distinct pillars to prevent "halo effects" (where excellent technical delivery masks poor team behaviour, or high morale obscures schedule slippages).
Technical Performance
Objective metrics tied directly to the baseline: Scope completeness, Quality (defect rates), Schedule adherence, and Cost/Budget performance.
Interpersonal Competency
The behavioural framework: Communication clarity, Cross-functional collaboration, Conflict management, and Decision-making efficacy.
Team Morale
The sustainability metric: Burnout indicators, voluntary engagement, and the capacity of the team to take on future work.
§2 Blank Template Structure
The standard assessment uses a simple three-tier rating system for every category: Exceeds Expectations, Meets Expectations, and Needs Improvement.
Part A: Technical Performance
| Dimension | Rating | Comments / Justification |
|---|---|---|
| Scope | [Document scope delivered vs. baseline] | |
| Quality | [Document defect rates, technical debt, compliance] | |
| Schedule | [Document milestone adherence and slack utilisation] | |
| Cost | [Document actuals vs BAC, contingency usage] |
Part B: Interpersonal & Morale
| Dimension | Rating | Comments / Justification |
|---|---|---|
| Communication | [Document reporting clarity and transparency] | |
| Collaboration | [Document cross-functional synergy] | |
| Conflict | [Document resolution mechanisms used] | |
| Decision Making | [Document consensus vs escalation velocity] | |
| Morale | [Document engagement and burnout indicators] |
§3 Worked Example: New Company Website
A realistic closeout assessment for a medium-scale digital delivery project (Mary's Consulting), demonstrating the required depth of justification for both "Meets" and "Exceeds" ratings.
Assessment Date: 18 Dec 2026
Technical Performance Outcomes
Scope
Team delivered all in-scope deliverables and absorbed two approved scope additions (CR-007 Press/Media; CR-008 LinkedIn icons) without quality compromise. Two page templates deliberately deferred to Phase 2 as a schedule trade-off. Note: Assessed as 'Meets' rather than 'Exceeds' because the deferral, while well-managed, represents a small reduction from the original baseline scope.
Quality
Outstanding quality outcome: 0 Sev-1/Sev-2 defects at launch, WCAG 2.1 AA passed cleanly, Core Web Vitals all green, 99.97% uptime through hypercare. The team's decision to build accessibility linting and performance budgets into CI from day one (LL-005, LL-011) is the strongest 'build quality in' demonstration recorded in this programme.
Schedule
Production Go-Live met on Nov 24, 2026 as planned. Team absorbed mid-project schedule pressure from CRM API discovery (I-006) by recovering through Phase 2 deferrals and parallel work. Schedule slack reduced from 7 to 2 days at peak stress but never breached.
Cost
Final cost $148,720 vs. BAC $142,952 (a computed +4.0% variance). Within $15K contingency reserve; $9,232 unused contingency returned to firm; $7,500 management reserve untouched. Cost overrun driven primarily by approved scope additions (CR-007), not by team performance issues.
Interpersonal Competency & Morale
| Dimension | Rating | Justification |
|---|---|---|
| Communication | Daily standups consistently focused and brief; weekly status reports always on time and substantive. Team self-surfaced bad news early (e.g., bio shortfall, CRM API gap) rather than hiding it. Sponsor and Marketing Lead both commented positively on communication clarity at the closeout review. | |
| Collaboration | Cross-functional pairing was the team's strongest trait. Examples: Bob and Bill paired on accessibility implementation; Christine and Marketing Lead partitioned the editorial review queue. The team operated as a single unit, not as siloed individual contributors. | |
| Conflict Management | Three notable conflicts during the project — none escalated to PM intervention. August brand-colour debate resolved through working session; September scope debate (CR-007) handled through formal change process. Team demonstrated ability to disagree productively. | |
| Decision Making | Team-level decisions made by consensus where possible; PM tie-broke when needed (rare). Domain decisions (tech, design, content) appropriately delegated to domain owners. Decision Log consistently maintained (14 tracked decisions with clear rationale). | |
| Morale | Morale stayed high throughout the project, including during the September stress period. Indicators: voluntary after-hours pairing on hard problems (positive sign driven by interest, not pressure); no sick-day pattern emerging during the build phase; 100% participation in retrospectives. |
§4 Areas for Development Formulation
The final element of a performance assessment extracts lessons learned into actionable development areas for the next project cycle. Always pair the observed Approach with specific, forward-looking Actions.
| Area | Observed Approach | Required Actions |
|---|---|---|
| Single-point dependencies | The team has key-person risk in each domain (tech, design, content). August leave (I-001) exposed this, though workarounds were successful. |
|
| Estimation on novel work | Three-point estimates were accurate on familiar work (LL-012) but significantly underestimated novel/complex work (A024 directory templates). |
|
| Earlier bottleneck escalation | The editorial review bottleneck (I-009) was visible 1–2 weeks before it formally surfaced. Earlier escalation would have permitted earlier mitigation. |
|
| Vendor technical discovery | The CRM API gap (I-006) cost approximately 5 days. A vendor technical-discovery call prior to estimation would have prevented this (LL-006). |
|