Sprint Efficiency compares what a sprint planned when it started with what it had completed when it closed. It's a planning-quality signal, not a productivity one.
What it measures
For every sprint that closed in the selected period:
Planned — the work in the sprint when it started.
Unplanned — work that entered the sprint after it started, including estimates raised mid-sprint.
Discarded — work taken out of the sprint before it closed, including estimates lowered mid-sprint.
Completed — work in the sprint that was in a done status when the sprint closed.
Carry-over — work still in the sprint and not done when it closed.
Planned + Unplanned − Discarded always equals Completed + Carry-over.
How Leanmote calculates it
Commitment met = Completed / Planned × 100
Story points or tasks. When a board estimates in story points, the card shows points; otherwise it shows tasks. When some board estimates, a toggle switches between both views.
Done means done at the close. Work finished after the sprint closed is carry-over of that sprint.
It can go above 100%. Unplanned work counts as completed when it's done, while Planned only holds what was there at the start.
Velocity is the average completed per closed sprint, with its minimum, its maximum and its change against the previous period. In story points it leaves out sprints with no estimated work, and the card says how many. A sprint with no work in it is listed but doesn't count in the velocity.
Team and person filters. With a team or person filter, the card counts only the sprints where those people had work, and only their work in them.
Sub-tasks and Azure DevOps Tasks are not counted on their own, the same way Jira and Azure DevOps leave them out of their sprint reports.
Done follows your status mapping in Leanmote, the same one every other metric uses.
What Show Details shows
For each sprint: its planned, unplanned and completed work side by side; every scope change with its date, author and points; and the tasks grouped by how they ended (planned, scope changes, completed, carry-over and discarded). You can export it all to CSV.
Important caveats
A sprint that started before Leanmote had the full history of its board is listed without numbers and left out of the totals.
Work that was already done when it entered the sprint is not counted as completed in it.
If your planning tool doesn't report when a sprint closed, that sprint is listed without numbers and left out of the totals.
Leanmote reads sprint history from Jira, Azure DevOps and Linear. Sprints from other planning tools are listed without numbers.
If you change the story points field of a board, its past sprints keep the points of the old field until they are recalculated. Contact support to recalculate them.
How to interpret it
Around 80–100% — the team plans roughly what it delivers.
Well above 100% — most of the work enters after the sprint starts. Look at Unplanned before reading it as good news.
Below 70% — over-commitment or discarded scope. Look at Discarded and Carry-over.
Volatile across sprints — usually scope changes, not effort. The scope changes in Show Details say what moved, when and who moved it.
What to do about it
Don't chase 100%. Optimizing for it incentivizes sandbagging.
Plan the sprint before starting it: what enters later shows up as Unplanned.
Use velocity, not a single sprint, to size the next sprint.
Related metrics
Throughput
Estimated vs Executed
Reworked Tasks