Work in progress

About this report

The Work in Process (by Team) report displays the overall progress of a selected sprint at the story level, providing a visual status of the stories by state, as well as an overview of the hours completed and remaining for delivery. 

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 process, mid sprint, without the need to interrupt valuable work. This report may also be beneficial as a tool during daily standups or during sprint review meetings as a mechanism for discussion.

The Report appears in 2 sections which include a Story by State section and a Development Progress by Rank section.

The first section appears as a table reflecting the 4 states defined within Jira Align as "Not Started", "In Dev", "In QA" and "Tested". Each state defined is represented in the column header, below which all of the stories currently within that state appear. Stories displayed in this section may appear Gray, Red, Yellow or Green. Hovering over any story will display the hours complete and hours remaining, as well as the story name.

• Stories "Not Started" appear Gray and are shown in the "Not Started" state on the kanban.
• Stories within the "In Dev" and "In QA" states may be Red or Yellow:
• Red stories are either started or not yet started, but are not expected to be complete within the sprint based upon current the estimate.
• Yellow stories are started but not yet complete, but whose estimates put them completing within sprint.
• Stories appearing in Light Green are Dev complete. 
• Stories appearing in Dark Green are Test complete or Accepted. 

The second section of the report, "Development Progress by Rank" displays the overall progress of the Sprint, as well as a detailed report of the progress by team member on pulled stories. The first row is a summary of the sprint which can appear Yellow or Green and when hovered over will display the number of man days in the form "Days Complete / Days Remaining" within the sprint.

Subsequent rows are a detailed report of team activity by team member:

1. The Row header contains a Photo of the Team Member, with the number of points committed in the sprint along with the percentage complete of the estimated work.
2. There are two rows adjacent to each row header that are stacked.
3. The first stacked element shows the Stories accepted by the team member, with the story number and expected completion date. Lengths of stacked elements are relative to estimated duration. Hovering over each story(stacked element) will display the story name, estimated hours and expected burn rate for the team member.
4. The second row of stacked elements displays the story number but also serves as both a fuel bar reflecting story completion and state (Dev or Test). Hovering over each story will provide the story name, state, rank status, time spent/time remaining (in hours), and total task time in hours.

Navigation

1. Select the Reports icon from the left Navigation menu.
2. Start typing the report's name in the Search box. 
3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

1. PI must exist within the system.
2. Sprints must fall within the selected PI. 
3. Stories must be assigned to the selected sprint. 

How are report values calculated? 

1. Hours Complete = Sum of Task Hours for completed Tasks
2. Hour Remaining = Sum of Estimated hours - burnt hours =  for incomplete tasks 
3. Days Complete = Round (difference between the sprint Due Date and the current date)
4. Days Remaining = Configured Sprint Length - Days Complete
5. Percent Complete = Days Complete / Configured Sprint Length
6. Percent Remaining = 100% - Percent Complete

Notes: 

1. Effort and value points for a story are credited on the day the story is accepted. 

How to interpret this report

Examination of the Sprint Kanban in this report shows all of the in-flight work as well as the Test-completed stories. In a single glance, you can see who is actively working on what, and which stories could potentially fall behind. Not started work the team can swam on, should team members with appropriate skills be available. Hovering over the Progress bar, can provide a high-level overview in the form of Days Complete and Days Remaining. This report can also be useful in workload balancing, by examining execution length for the work load consumed by each team member. Team members overloaded can be off-loaded to provide a better overall velocity.