Team Assessments: the Good, the Bad and the Ugly
summary
Compares lightweight Spotify squad health check and the deeper agile coaching growth wheel, then describes building a 23‑topic internal assessment in a Google sheet, run quarterly with two sessions: guided fill-in and a retrospective; results stay anonymized and mix subjective ratings with objective metrics (cycle time, throughput, sprint goal success rate target 80%, blocker resolution thresholds such as average >5 days). Explains voluntary rollout, cross-team aggregation without team labels, and that this combination actually improves clarity and measurable progress.
AI-written summary · about
chapters (13)
- 0:00Team assessments introduction
- 1:52Why teams start with assessments
- 3:59Assessments gone wrong
- 5:02Tools resistance
- 8:50Managers blind spots
- 10:57Purpose vs metrics
- 13:04Self-assessment core
- 15:50Balancing lightness
- 17:13Regular check-ins
- 19:42Clear expectations
- 20:44Context-specific assessments
- 22:11Subjective and objective data
- 23:34Q&A
related talks
42mMeasuring Agile success
49mAgile Team Performance Management
44mMeasuring agility: Data analytics ex psychology to grow your teams agility
40mAmplifying Agile Quality Practices
27mIntroducing the Platform Maturity Assessment
41mRethinking Measurement for High-Performing Teams
44mPerformance Management: the new team responsibility
31mStop Breaking Your Teams: Seeing the Whole Instead of Pieces