Versions Compared

Old Version 2

changes.mady.by.user Pranav Barar (Unlicensed)

Saved on

compared with

New Version 3

changes.mady.by.user Pranav Barar (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

KPI Name

Iteration Commitment

Work Remaining 

Definition (info)

Iteration commitment shows in terms of issue count and story points the Initial commitment (issues tagged when the iteration starts), Scope added and Scope removed.

Calculation Logic

The widget should show

  1. Initial Commitment

  2. Scope added

  3. Scope Removed

  • Initial Commitment widget will show the data of Issues completed + not completed + scope removed - scope added for the Iteration.

  • Scope added widget will show the data added issues for the sprint - The issues with * symbol from sprint report.

    • Scope removed widget will show the removed issues from the sprint - The issues from Scope removed collection from sprint report.

    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 IdID

    2. Issue Description

    3. Issue Status

    4. Issue Type

    5. Size (story pointStory Point/hoursHours)

    6. Original Estimate

    7. PriorityRemaining Days

    8. Due Date

    9. Original Estimate

    10. Remaining Estimate

    11. AssigneePredicted completion date

    12. Potential delay (in days)

    Configurations