Page Comparison

Definition (Hover Text)

Displays the cumulative daily progress planned dues of the release in relation to the overall Release scope. Users get to forecast the prediction completion of the Release. Alternatively, they can you check when development will be completedbased on the due dates of work items within the release scope.

Additionally, it provides an overview of the entire release scope.

Source Tools

Jira

Graph type

Line

Y-Axis: Issue Count or Story Points (based on filter selection)

X- Axis: Days or Weeks or Months

FiltersSelection between Issue Count and Story Points

N/A

Hover Format on KPI

• Release Scope: Issue Count or Story Points

• Release ProgressPlan: Issue Count or Story Points

• Release Prediction: Issue Count or Story Points

Fields on Overlay

1. Issue ID

2. Issue Type

3. Description

4. Size

5. Priority

6. Assignee

7. Issue Status

8. Due date

Business Logic

Calculation Formula

• Based on the business logic of number of issues closed in the previous days, the graph should project a completion date.

  • By Previous days, default consideration should be to consider 

    • No. of days in the Past between Start Date of Release & Today

    • If No. start date, then consider the graph plot when the first issue tagged to the release was closed

    • Based on the No. of working days between First graph plot date and today, calculate daily average in terms of issue count and story points

    • Based on this daily average of past, predict the predicted completion date of release in future (considering only future working days)

• Release Progress and Prediction logic based on

  • Overall Completion

  • Dev Completion

Trend

• If Release Start Date is not available, then Start Date marker will not be available

• Final Due Date marker is the date by when all issues of the release are due

Trend

1. Overall Release Scope

2. Release Plan as per planned due dates

Markers

1. Today

2. Release Start Date

3. Final Due Date

4. Planned Release Date

Maturity Levels

N/A

Instance level thresholds

N/A

Configurations

Processor Fields

KPI Specific fields

Count of days from the Release start date to calculate closure rate of predictionN/A

How to Validate KPI

Suggested ways of working

Sample JQLs

Benefits of KPI

How does the KPI help

1. Identify whether all issues planned in the release scope are due to be completed on/before the scheduled release date.

2. Identify whether the release scope changes are impacting the final due.

3. Help you discover and descope a few non-critical issues to keep your release plan on track.