This Team Performance Assessments Software Development workbook records the sprint-by-sprint performance measurements Eduardo Montes used to evaluate the ProjectAdm development team — velocity, defect escape rate, code review throughput, and satisfaction scores for all seven team members across 28 sprints, from Marcus Webb's backend throughput to Lucas Park's QA regression coverage. Team performance assessment is how a Scrum Master knows whether the team is growing, stagnating, or burning out.

What Are Team Performance Assessments?

Team Performance Assessments are a PMBOK 8 output in the Team Performance Domain representing the evaluation of how effectively the team is performing as a unit and how individual team members are developing their skills and capabilities. Assessments cover both quantitative metrics (velocity, throughput, defect density, cycle time) and qualitative dimensions (collaboration, communication, psychological safety, morale). PMBOK 8 distinguishes between individual performance evaluations (a management responsibility) and team performance assessments (a project leadership responsibility) — the latter focus on the team as a system, identifying bottlenecks, knowledge silos, and collaboration breakdowns that no individual metric captures alone.

What This Team Performance Assessments Software Development Includes

The ProjectAdm Team Performance Assessments workbook contains five worksheets:

• Velocity Dashboard — Story points committed vs. completed per sprint for the full team; individual contribution by team member; velocity trend (3-sprint rolling average); sprint goal achievement rate (achieved / partially / missed)
• Quality Metrics — Defects found in QA (Lucas Park) vs. defects escaped to UAT per sprint; defect escape rate (%); code review turnaround time (average hours from PR open to merge) by reviewer; test coverage % per sprint
• Collaboration Indicators — Cross-functional pair-programming sessions per sprint; knowledge-sharing sessions (tech talks, retrospective action items implemented); blocked days per team member (days waiting on a dependency); ISS-003 (Safari drag-drop) assigned to Julia Chen + Bruno Silva cross-functional pair
• Team Health Pulse — Bi-weekly 5-question anonymous survey (scale 1–5) covering workload, clarity, autonomy, collaboration, and growth; team average and individual anonymized scores; Sprint 7 dip (avg 3.1) triggered Eduardo's "sustainable pace" retrospective action
• Individual Development Log — Skills development goals set at project start vs. actual progress by Sprint 28; Camila Rocha: accessibility expertise; Marcus Webb: query optimization; Julia Chen: WebSocket implementation; Bruno Silva: CI/CD pipeline

How Eduardo Montes Used This Team Performance Assessments Software Development

Eduardo Montes used the Team Performance Assessments workbook as the primary input to Sprint Retrospectives. The velocity dashboard revealed a pattern Eduardo wouldn't have spotted without data: Marcus Webb's backend velocity was high in Sprints 1–4 but dropped 30% in Sprint 5 (ISS-002 investigation) and recovered only to 80% of baseline in Sprints 6–8 — indicating that the MariaDB performance issue was consuming residual attention even after the immediate fix. Eduardo responded by temporarily reassigning Bruno Silva to backend support, which freed Marcus to fully focus on the optimization, and velocity returned to baseline by Sprint 10. The team health pulse survey's Sprint 7 dip (3.1 average) was the early warning sign that motivated the "no after-hours Slack" policy — implemented in Sprint 8 and reflected in a recovery to 3.9 by Sprint 10.

How to Use This Team Performance Assessments Software Development Document

When building your own Team Performance Assessments Software Development tracker, resist the temptation to use it as a performance management tool for HR purposes. PMBOK 8 is explicit: team assessments are for improving the team system, not for ranking individuals. The ProjectAdm workbook was shared transparently with the entire team — every team member could see the velocity dashboard and the anonymized health pulse scores. This transparency created psychological safety: team members raised blockers earlier because they trusted that the data would be used to remove obstacles, not to judge them.

Ready to create your own team performance assessment? Download the blank Team Performance Assessments Template (PMBOK 8).

• Download the Team Performance Assessments Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Team Performance Assessments in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Team