Versions Compared

Old Version 2

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

Saved on

compared with

New Version Current

changes.mady.by.user Roopa P

Saved on

Key

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

KPI Name

Iteration Commitment

Issues likely to spill

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 removedIt gives intelligence to the team about number of issues that could potentially not get completed during the iteration. Issues which have a Predicted Completion date > Sprint end date are considered.

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.

    This widget shows number of issues likely to spill.

    It is based on the logic of remaining estimate of an issue and comparing it with the remaining time in the sprint. 1 day considered as 8 hours

    Filters

    Filter by issue Issue type

    Filter by StatusPriority

    Columns in Overlay Screen

    1. Issue IdID

    2. Issue DescriptionType

    3. Issue StatusDescription

    4. Issue TypePriority

    5. Size (story pointStory Point/hoursDays)

    6. PriorityIssue Status 

    7. Due Date

    8. Original Remaining Estimate

    9. Remaining Estimate

    10. Assignee

    Configurations

    2. Predicted Completion Date

    Configuration

    Processor Fields

    NA

    Mandatory fields

    NA