Sprint Efficiency measures how much of the team's sprint scope actually completed in the period. It's a planning-quality signal, not a productivity one.
What it measures
The share of in-scope tasks that finished within the period, counted at the task level (not story points).
How Leanmote calculates it
sprint_efficiency = completed_sprint_tasks / total_sprint_tasks * 100
Counted as tasks — not story points. Story-point variants are not configurable today.
Numerator — tasks whose latest status sits in a "done" state with a status log inside the selected period.
Denominator — tasks in sprints active during the period plus tasks not assigned to any sprint. The denominator reflects the current state of the scope, not a snapshot taken at sprint start.
Empty denominator — if the team has no sprint tasks in the period, Sprint Efficiency is reported as 0.
Important caveats
Because tasks not assigned to any sprint count toward the denominator, teams with a lot of tasks without a sprint will see lower Sprint Efficiency even if their planned scope is on track. Triage and label your work in your planning tool to keep the denominator clean.
Because the denominator is the current scope (not a sprint-start snapshot), tasks added or removed mid-sprint change the percentage retroactively. Treat single-sprint readings carefully and look at trends across several sprints.
How to interpret it
80–100% — healthy. The team commits to roughly what they can deliver.
Below 70% — chronic over-commitment, scope creep, or a denominator inflated by tasks without a sprint. Look at both before reacting.
Volatile across sprints — usually mid-sprint scope changes, not effort fluctuation.
What to do about it
Don't chase 100%. Optimizing for that incentivizes sandbagging.
Audit tasks without a sprint regularly so the denominator reflects intent, not noise.
Track Sprint Efficiency together with mid-sprint scope changes — the gap usually explains the variance.
Related metrics
Throughput
Estimated vs Executed
Reworked Tasks