Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 5 Next »

Overview

Definition (Hover Text)

Scope churn explains the change in the scope of sprint since the start of iteration

Source Tools

Jira, Azure

Graph type

Line

Filters

Story Points, Issue Count

Hover Format on KPI

Sprint Name:  <<Value>>

Fields on Overlay

  • Sprint Name

  • Issue ID

  • Issue type

  • Issue Description

  • Size

  • Scope change date

  • Scope change (Added/Removed)

  • Issue status

Business Logic

Calculation Formula

(Stories added + Stories removed) / Count of Stories in Initial Commitment at the time of Sprint start

Trend

Higher the scope churn, lesser is the Speed

Maturity Levels

M1: >50%

M2: 30-50%

M3: 20-30%

M4: 10-20%

M5: <10%

Instance level thresholds

Configurations

Processor Fields

NA

Mandatory fields

Issue type to identify Story

How to Validate KPI

Suggested ways of working

Sample JQLs

NA

Benefits of KPI

How does the KPI help

  1. Highlighting changes in project requirements or scope.

  2. Allowing teams to assess the impact of changes on timelines and resources.

  3. Facilitating proactive management of project scope to minimize disruptions and maintain project goals.

C

  • No labels