About this report
The WIP (Work in Progress) by Step report displays doughnut charts comparing the counts of various Value Stream process steps (for example, ready to build, market research, feasibility study) 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 process steps, 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 process step 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 process steps for 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.
- 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.
- Themes must exist in the system.
- Epics must be created and tied to a primary program and theme.
- Features must be created and assigned to program increments.
- Features must be created and assigned to epics.
- Value Stream process steps must be created and defined for epics and features.
How are report values calculated?
- Epic process step counts are pulled from the Epics page/Epic panel.
- Feature and Stand-Alone Feature process step counts come from the Features page/Feature panel.
- Process steps are defined on the Value Stream page.
How to interpret this report
Charting the process 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 team 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 research and testing at the end.