Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Overview

Definition (Hover Text)

Displays the cumulative daily planned dues of the release based 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

X- Axis: Days or Weeks or Months

Filters

N/A

Hover Format on KPI

  • Release Scope: Issue Count

  • Release Plan: Issue Count

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

  • Default considerations are:

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

  • Final Due Date marker is where the last issue tagged to the release is due to be completed

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

N/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.

  • No labels