Estimated vs Executed compares the estimated effort on completed items to the actual time those items consumed. It's the most direct measure of estimation accuracy across a period.
What it measures
How much of the estimate the work actually consumed, as a percentage: executed time over estimated hours.
How Leanmote calculates it
estimated_vs_executed = (executed_hours / estimated_hours) * 100
executed_hoursis invested hours by default, or worked active time if your organization set that basis.Reported as a percentage, where 100 means estimates matched reality — not a ratio around 1.0.
Weeks with no estimated hours are left empty rather than counted as zero.
How to interpret it
Above 100% — the work consumed more time than estimated. Common in teams that don't include review, QA and deploy in the estimate.
Below 100% — the work consumed less than estimated. Could be padding, or could mean efficient delivery.
Stable around 100% across periods — estimates are well-calibrated.
What to do about it
Don't react to single-period swings. The signal is in 4–8 week trends.
If consistently below 1.0, expand the scope of "estimate" to include review and QA.
If wildly inconsistent, the team is probably mixing estimate units or item types — split by item type and re-check.
Related metrics
Estimated Hours
Invested Hours
Sprint Efficiency