The Sprint Summary commitment lock marks the end of Day 2 of a sprint — the point after which scope additions and removals are tracked as intentional changes. Before that lock is reached, sprint scope is still being assembled, so counting +N or -N changes is misleading. Two bugs in how the extension handled the pre-lock period have been corrected in 3.7.2.
Bug 1: False +1 Before Day 2
When a new item was added to a sprint on Day 1 — before the commitment lock — the Scope Change tile was showing +1. This happened because the baseline snapshot used at sprint start did not yet include items added that day, and the tile was comparing the current sprint contents against that earlier snapshot without checking whether the lock had passed.
- The tile now checks whether the commitment cutoff has been reached.
- Before Day 2 ends, the tile shows "—" instead of a change count.
- A message below the tile reads "Commitment lock not yet reached — scope change is tracked after end of Day 2".
- Once Day 2 ends, the tile works exactly as before — tracking all net additions and removals against the committed baseline.
Bug 2: Pre-Cutoff Items in the Removed Panel
The "removed from sprint scope after Day 2" slide-out panel was showing items that were removed before the commitment lock, not after it. This happened because when a removal timestamp was not available, the extension fell back to using today's date — making any item without a confirmed timestamp appear to have been removed after the lock.
- The panel now requires a confirmed post-cutoff removal timestamp before including an item.
- Items removed before Day 2 no longer appear in the panel at all.
- The wording has been updated from "removed mid-sprint" to "removed from sprint scope after Day 2" to match the intent of the feature.
Why Commitment Lock Accuracy Matters
The commitment lock is one of the most important reference points in sprint analytics. It separates 'we were still planning' from 'we changed the plan'. If the scope change tile fires before the lock is set, or the removed-items panel shows items that left before anyone committed to them, the data loses its meaning. These fixes ensure the tile and panel only reflect deliberate mid-sprint changes.
Both fixes are included in Agile Analytics 3.7.2. Update from the VS Marketplace to get them.