Work Remaining

Definition

Remaining work in the iteration in terms count of issues & sum of story estimates. Sum of remaining hours required to complete pending work.

Calculation Logic

Issue count - Total no. of issues that are not completed.

Story Points - Sum of story points of all issues not completed

Hours - Sum of remaining hours of all incomplete issues in Jira

Potential Delay - Show in Days (sum of max. delay of each assignee)

Source of this KPI is Jira. To see the latest data, run the Jira processor from KnowHOW settings

The Delay of in progress stories was getting add up to subsequent stories, so we have changed the logic as per below

On Overlay we are showing delay of all the stories, but on kpi, calculation of only in progress stories are applied

In Active sprint

** - *(1)* {+}In progress stories{+}: the delay will be calculated as per today's date i.e., todays's date + remaining estimate, for all the stories marked as *in progress* -
** - {+}in Open stories{+}-the remaining stories are considered as open stories, sort open stories by due date. -
*** - the last PCD which we got from *(1)* will be used to calculate the pcd for open story as a starting point, -
*** - the subsequent story delay will be calculated from the last pcd of the open story -
*** - if 2 stories having same due date the one having maximum pcd will be used for further calculation{*}{{*}} -

• - *In closed sprint* -  

**   - the delay in all the stories will be calculated from sprint end date + remaining estimate

Filters

Filter by issue type

Filter by Status

Columns in Overlay Screen

1. Issue ID

2. Issue Description

3. Issue Status

4. Issue Type

5. Size (Story Point/Hours)

6. Original Estimate

7. Remaining Days

8. Due Date

9. Predicted completion date

10. Potential delay (in days)

Configuration

Processor Fields

NA

Mandatory fields

NA