WIP by state

About this report

The WIP (Work in Progress) by state report displays doughnut charts comparing the counts of various states (not started, in progress, accepted, etc.) of epics, features, and stand-alone features for a specific PI. Doughnut charts show the relationship of parts to a whole--in this case, the count of epics, features, and stand-alone features in specific states, compared to the sum of all epics, features, or stand-alone features, respectively. Simply hover over a doughnut segment to see the count and percentage of a state compared to the whole.

The report is especially useful to both Scrum Masters and product owners, who are seeking an unobtrusive approach for examining the status of work in progress, mid PI, without the need to interrupt valuable work. This report may also be beneficial as a tool during daily stand-ups or during sprint review meetings as a mechanism for discussion.

The report starts with charts depicting the WIP states of all epics and all features in the selected PI, and then provides epic and stand-alone feature charts for each program the selected PI is tied to.

To navigate to this report:

1. Select Portfolios, Solutions, or Programs in the top navigation bar and select the entity you want to view information about.
2. On the sidebar, select Reports in the list of options.
3. Select Work in progress by state; the report displays.

Prerequisites 

1. PI must exist in the system and be tied to a program. 
2. Themes must exist in the system. 
3. Epics must be created and tied to a primary program and theme.
4. Features must be created and assigned to program increments. 
5. Features must be created and assigned to epics. 

How are report values calculated? 

1. Epic state counts are pulled from the epics page/Epic panel.
2. Feature and Stand-Alone Feature state counts are pulled from the features page/Feature panel.

How to interpret this report

Charting the life cycle of an epic or feature is vital for checking the status of development and team velocity in a PI. The goal of any PI is to have as many (or all) of the epics and features in an Accepted state by the end, which is desired before the PI review. Accepted epics and features demonstrate that all acceptance criteria have been met by the sprint teams, and deadlines are being met. Scrum Masters and product owners should look for a steady cadence of these work items moving through the life cycle during a PI, as opposed to high volumes of testing and acceptance taking place at the end.