Understanding Team Productivity
How we calculate. Productivity % = (delivered ÷ capacity) × 100 for the same unit and sprint. The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Team Productivity case uses delivered output 36 and planned capacity output 40. Enter the same figures below to reproduce the worked path.
What is Team Productivity?
A throughput ratio against capacity—not a quality score. High productivity with rising reopen rates is still a problem; pair with QA metrics.
- Capacity output is what you planned to pull, not wishful stretch
- >100% can mean under-estimation or unpaid overtime—investigate
- Use with velocity for forecasting, not ranking people
The Formula
Worked Example
Common Use Cases
- Sprint review: delivery vs capacity at a glance
- Process health: chronic low % signals blockers
- QA throughput: cases completed vs planned capacity
Pro Tips
- Exclude forced overtime from “healthy” >100% narratives
- Normalize units — do not mix points and tickets
- Combine with fail/reopen rates for a balanced scorecard
Limitations: Team Productivity results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.
FAQ
Is this individual performance?
No. Keep it at team level. Individual scoring with this metric encourages sandbagging.
Capacity vs velocity?
Capacity is what you could take this sprint. Velocity is historical average delivery. Productivity compares delivered to this sprint’s capacity.
Authoritative References
For Agile and software testing practices, consult:
- Scrum.org — Scrum glossary and sprint practices
- ISTQB — software testing glossary
- Agile Manifesto — values behind iterative delivery