Sprint Efficiency measures how much of the work a team committed to at the start of a sprint actually got completed. It's a planning-quality metric, not a productivity one.
What it measures
The ratio of completed tasks to the tasks committed at sprint start.
How Leanmote calculates it
sprint_efficiency = completed_tasks_in_sprint / committed_tasks_at_sprint_start
Committed scope is captured at sprint start. Tasks added mid-sprint don't change the denominator.
Completed scope is the count of tasks in done states by sprint end.
Counted at the task level, not story-point level.
How to interpret it
80–100% — healthy. The team commits to roughly what they can deliver.
Above 100% — the team consistently overdelivers, which usually means under-committing or pulling unplanned work.
Below 70% — chronic over-commitment, scope creep, or interruptions. Examine the pattern before adjusting commitments.
What to do about it
Don't chase 100%. Sprint Efficiency optimized for that incentivizes sandbagging.
Track Sprint Efficiency together with mid-sprint scope changes — the gap often explains the variance.
Address process before behavior — efficiency drops are often caused by unplanned support work, not under-effort.
Related metrics
Throughput
Story Points
Estimated vs Executed