About this report
The stories by state report shows how many stories are in each state (In Progress, Dev Complete, Test Complete, Accepted) for a specific PI. The report provides this information in the form of a line graph. Information is graphed on an X and Y axis, using data points connected by line segments. This report is beneficial to Scrum Masters, team leaders and members, and product owners to compare volumes as stories progress through the various states during a sprint. It is beneficial to review the report with team members during sprint review meetings and daily standups. This report is generated by selecting a specific sprint within a PI.
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 information about.
- On the sidebar, select Reports in the list of options.
- Select Stories by state; the report displays.
If you’re using the old navigation:
- 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.
- Sprints must be created and tied to a PI.
- Teams must be created and tied to a program.
- Stories must be assigned to sprints.
How are report values calculated?
- Story state is pulled from the stories page/New Story panel, or Kanban board, if category/column is mapped to work item state when used.
- Sprint dates are pulled from the Sprint List/New Sprint panel.
How to interpret this report
Charting the life cycle of a user story is vital for checking the status of development and team velocity in a sprint. The goal of any sprint is to have or all of the team's stories in an Accepted state by the end of the sprint, which is desired before the sprint retrospective. Accepted stories demonstrate that all acceptance criteria have been met by the sprint team, and deadlines are being met. Scrum Masters and product owners should look for a steady cadence of stories moving through the life cycle during a sprint, as opposed to high volumes of testing and acceptance taking place at the end of a sprint.