About this report
The split analysis report shows how many story splits occurred for a team, by sprint, in a PI. The report not only displays a count of splits for each sprint, but a list of the actual splits as well, including name and description.
If a story cannot be completed in a sprint as planned, then you have the option to split the story. When splitting the story, you can assign the remaining uncompleted items to a split story in a future sprint. You can only split a story one time.
This report is beneficial to Scrum Masters, team leaders and members, release train engineers, and product owners to see where splits are being used by teams during sprints in a PI. It is beneficial to review the report with team members during pre- and post-PI meetings, daily stand-up meetings, and during sprint review meetings. This report is generated by selecting a team.
To navigate to this report:
If you’re using the new navigation:
- Select Teams in the top navigation bar and select the team you want to view the report about.
- On the sidebar, select Reports in the list of options.
- Select Split story analysis; the report displays.
If you’re using the old navigation:
- Select the Reports icon from the left Nav 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 must be created and tied to features.
- Stories must be assigned to sprints.
- Sprints must be created and tied to a PI.
- Teams must be created and tied to a program.
How are report values calculated?
- Split counts, names, and descriptions are pulled from the Story Management Options page; stories are split by clicking the More Options link on a Story panel, and then clicking the Split button.
- Sprint sync dates are pulled from the sprint list/New Sprint panel.
How to interpret this report
A high number of splits in a sprint, or by a specific team, requires investigation. This usually indicates stories were blocked, not dev complete, not tested, or delayed by a dependency.