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.

Productivity % = (delivered ÷ capacity) × 100 for the same unit and sprint.

Tip: Keep “Delivered Output” and “Planned Capacity Output” on the same basis (units, period, and definition) before you calculate.

Cluster: Software Testing hub · Professional KPIs · Percentage guide

Team productivity compares what was delivered to what the team had capacity to take on.

Enter delivered points (or items) and the capacity planned for the same sprint.

Points or items finished this sprint
Output the team had capacity to pull

Productivity %

Understanding Team Productivity

How we calculate. Productivity % = (delivered ÷ capacity) × 100 for the same unit and sprint. 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

Team Productivity
Productivity % = (Delivered output ÷ Capacity output) × 100

Worked Example

Scenario: The team delivered 36 points against 40 points of planned capacity.
Step 1: Delivered = 36
Step 2: Capacity = 40
Step 3: (36 ÷ 40) × 100 = 90%
Answer: Team productivity is 90%.

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
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

Limitations: Team Productivity results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

The worked example for team productivity was verified with the calculator form on this page—enter the same values to confirm the result.

When to use this calculator

  • Use this page when your wording matches team productivity and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about team productivity? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this team productivity calculator?

For team productivity, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for team productivity—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking team productivity, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

Authoritative References

For Agile and software testing practices, consult: