About this report
The Scope Change report is a report that captures changes to scope of work for the selected team during the defined sprint. The report is beneficial to Scrum Masters for monitoring changes during the sprint to ensure teams can deliver against the targeted scope of work. It will be beneficial to review this meeting prior to the daily stand-up and throughout the sprint to address any changes in scope that make impact the teams ability to deliver their sprint commitments.
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system, and be tied to a program.
- Features must be created and tied to the PI.
- Stories, with point values, must be created and tied to features.
- Stories must be assigned to sprints.
- Sprints must be created and tied to a PI.
- Tasks must be created and assigned to stories.
- Teams must be created and tied to a program.
How are report values calculated?
- Active Defects = Total number of active defects on the first day of the sprint plus any new defects introduced during sprint reduced by the number of defects closed during sprint.
- Task Hours = Total task hours on the first day of the sprint plus any increase in task hours minus any task hours that are burned down.
- Story Count = Total number of stories committed during sprint planning plus any new stories added to the sprint less the number of accepted stories during sprint.
- Impediments = Total number of impediments on the first day of the sprint plus any new impediments throughout the sprint reduced by the number of impediments removed during sprint.
- Risks = Total number of risks on the first day of the sprint plus any new risks introduced during the sprint reduced by the number of risks resolved during the sprint.
- Task Count = Total number of tasks on the first day of the sprint plus any new tasks introduced during the sprint reduced by the number of risks resolved during the sprint.
Additional disciplines that are assigned to a PI will also show up on the graph. Up to 3 disciplines can be added to a PI, for team members to enter time against outside of the story work. In the example below, Dev Count and Customer Support display as disciplines.
How to interpret this report
The report should be used to determine if the team is being disrupted during the sprint by scope changes. Team disruptions during a sprint should be limited and all disruptions put a greater risk on successful delivery of sprint commitments. Small increases in scope defect is normal throughout a sprint; however if a large number of defects are created it may signal a need to further investigate the root cause. Items such as poorly written stories, not utilizing test driven development, etc. are items that can increase the number of defects. Slight increase in task hours can be expected within a sprint but it a large number is present this could be a result of new work being introduced or team not having a clear understanding of the story while tasking during sprint planning.
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.