Most sprint summary tools read your current board to compute what happened during a sprint. That approach has a well-known problem: items that were removed mid-sprint simply disappear. Sprint Summary in Agile Analytics takes a different approach — it reconstructs the sprint from System.IterationPath revision history using the EVER WIQL keyword, so nothing is lost.
How the Committed Set Is Defined
A common challenge in multi-timezone or distributed teams is that sprint planning often extends into day 2 as late refinements land. Sprint Summary accounts for this by locking the committed set at the end of day 2 of the sprint — not at the sprint start date. Items added after that point are classified as scope additions, not original commitment.
Scope Change That Makes Sense
Scope change is reported as net additions and net removals separately. Items that left and came back within the sprint (bounces) are treated as neutral — they do not inflate either number. This gives you a cleaner picture of genuine planning discipline versus noise.
Carryover Based on Workflow State
Carryover is determined by the item's workflow state position at sprint end, not by whether an estimate field was filled in. If an item was in an active or in-progress state when the sprint closed, it counts as carryover — regardless of story points.
Removed Items Panel
Every item that was in the sprint commitment and was subsequently removed is listed in the Removed Items Panel. Each entry shows the item title, type, and the state it was in when it was removed. This makes sprint retrospectives and scope accountability conversations much easier.
Multi-Team Comparison and CSV Export
Sprint Summary supports multi-team comparison mode with independent sprint selectors per team. You can export the full summary to CSV for stakeholder reporting or archiving. This is particularly useful for program-level reviews where multiple teams are being assessed simultaneously.