Avium SignalsTeam tier and above

Sprint Scope Change — track mid-sprint adds and removes with receipts

'We committed to X, we shipped Y' is half the conversation. 'Here's what got added on day 6 and what got dropped on day 8' is the other half. Avium has it.

The retro nobody wins

Sprint review. You committed to 25 story points. You shipped 18. Leadership wants to know why. The team starts naming things: 'a P0 came in,' 'we lost two days on a regression,' 'one ticket grew.' Each one feels reasonable individually; in aggregate, you missed by 28%. Nobody can prove which factor mattered most.

Without a record, every retro is anecdote. With a record, the conversation shifts from 'who's to blame' to 'how do we estimate scope-change risk into the next sprint.'

How teams try to track scope change today

Methods that work for one sprint and decay by the third:

A spreadsheet started at sprint planning — by week 2, nobody updates it.
Jira's Sprint Report shows added/removed totals as numbers but not as a list of WHICH tickets — useless when leadership wants specifics.
Asking the team at retro: 'what got added' — the team forgets. Memory is compressed.
Eyeballing the sprint burndown for upward kinks: tells you SOMETHING changed but not what.

How Avium Signals computes sprint scope change

Avium reads the sprint field change history on every ticket. Every ticket added to or removed from a sprint after the sprint started is logged.

Added mid-sprint: tickets whose sprintId changed to the current sprint AFTER the sprint's startDate. Lists ticket key + summary + when it was added.
Removed mid-sprint: tickets whose sprintId was the current sprint at start but no longer is. Same detail.
Net scope delta: added story points minus removed story points. Positive = scope grew; negative = team de-scoped to make it.
Net scope creep percentage: delta as a percent of the original commit. Avium escalates the Signal when creep exceeds 15%.

Who reads this Signal

Scrum masters

Retro evidence. Walk in with the list of what changed. The conversation goes from 'we missed' to 'here's the data on scope dynamics.'

Agile coaches

Coach the planning practice when scope creep is structural. A team that adds 20% every sprint isn't bad at execution; it's bad at planning. The data names which one.

Engineering managers

Push back on mid-sprint adds with evidence. 'We added X points to your sprint last time and you missed by Y' is a harder conversation to lose.

VPs of engineering

Cross-team scope-change patterns. If one PM is consistently adding mid-sprint and that team consistently misses, the leadership conversation has a name on it.

See what changed in your last sprint

Free tier shows the scope-change signal on demo data. Once your work management tool is connected (Jira today, more integrations on the way), Avium reads sprint history and surfaces the deltas immediately. Available on Team and above.

Start free — no credit card →

Related Avium Signals

Sprint Risk Forecast

Stop finding out at sprint review. Avium Signals reads your Jira data — or any work management tool — and forecasts which sprints are about to miss — and why.

Velocity Drift

Velocity is the metric every VP asks about and no team trusts. Avium Signals tells you when it's actually shifting — and whether the shift is structural or noise.

Data Quality Score

Your forecast is reading from your data. If your data is broken, the forecast is too. Avium scores the gap.