Story audit report

About this report

The Story Audit Report shows which stories are associated with a PI as well as story status. The report is beneficial to Scrum Masters, team leaders and members, and product owners for assessing and tracking story progress during a PI. It is beneficial to review the report with team members during team ceremonies that take place during a PI, such as Sprint Review Meetings. This report is generated by selecting a specific PI, optionally within a specific program.

Prerequisites

1. PI must exist in the system and be tied to a program. 
2. Stories must be created and assigned to sprints. 
3. Stories must be created and assigned to features. 

How are report values calculated? 

• Story ID = ID of story in the selected PI; auto-assigned at story creation.
• Story Name = Name of the story in the selected PI; created via the Story Grid/New Story panel.
• Type = Type of story, such as user or defect; assigned via the Story Grid/New Story panel.
• PI = PI in which the story resides; selected via the Story Grid/New Story panel
• Sprint = Sprint in which the story resides; assigned via Sprint Planning.
• Feature = Feature in which the story resides; assigned via the Feature Grid/New Feature panel.
• Date Created = Date when the story was created; value is pulled from Story Grid.
• Pending Approval = Date when the story went to the Pending Approval state; value is pulled from Story Grid.
• In Progress = Date when the story went to the In Progress state; value is pulled from Story Grid.
• Dev Complete = Date when the story went to the Dev Complete state; value is pulled from Story Grid.
• Test Complete = Date when the story went to the Test Complete state; value is pulled from Story Grid.
• Accepted = Date when the story went to the Accepted state; value is pulled from Story Grid.
• Accepted By = Person who accepted the story; value is pulled from Story Grid.

How to interpret this report

Early in a PI, stories will be in the Pending Approval state. As the PI progresses, stories should move through the approval process and advance through the In Progress, Dev Complete, and Test Complete states. Ultimately, at the end of the PI, all stories should be in the Accepted state. If a large number of stories are not in the Accepted state at the end of the PI, resources, story points, and sprint planning should be re-evaluated for the next PI--this also holds true if all stories are in the Accepted state well before the end of the PI. Use this report to achieve the goal of creating a development cadence, which will provide predictability and confidence in future work.