detect-scope-change

Sprint scope change percentage is calculated by detecting tickets added or removed after the sprint start date, computing the net story point change against original committed story points, and classifying the impact as stable, moderate, significant, or critical.

Sprint scope change impact classification categorizes sprint stability into stable, moderate, significant, and critical levels by quantifying the story points added or removed mid-sprint, providing a clear metric for sprint reviews and retrospective reporting.

Detect mid-sprint scope changes by providing a list of sprint tickets and the sprint start date to identify tickets added after the start date using added_to_sprint or created dates, then computing the net story point difference to generate a scope change report.

Yes, you can track removed tickets separately by providing an optional removed_tickets input alongside sprint_tickets and sprint_start_date, allowing the report to compute both added story points and removed story points for a complete scope change analysis.

A sprint scope change report includes original committed story points, added story points, removed story points, net scope change percentage, and an impact classification to assess sprint predictability and stability for retrospective analysis.

Generate a scope change report during agile sprint reviews and retrospectives when you need to assess sprint stability by quantifying tickets added or removed after the sprint start date and evaluating their impact on original story point commitments.