Versions Compared

Version Old Version 2 New Version 3
Changes made by

Pranav Barar (Unlicensed)

Pranav Barar (Unlicensed)

Saved on

Key

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

KPI Name

Iteration Commitment

Estimate vs Actual

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 removedEstimate vs Actual gives a comparative view of the sum of estimated hours of all issues in an iteration as against the total time spent on these issues.

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.

    Shows 2 data points

    1. Original Estimates - Derived from Actual Estimate field in Jira

    2. Logged Work - Logged work field in Jira 

    The above information should be summed up for all issues in the selected sprint

    This KPI can be filtered based on

    1. Issue type (Multi-select)

    2. Priority (Multi-select)

    Both work in combination ℹ

    • Estimate vs Actual

    Filters

    Filter by issue typeFilter by Status

    Columns in Overlay Screen

    1. Issue IdID

    2. Issue Type

    3. Description

    4. Issue StatusIssue Type

    5. Size(story point/hours)

    6. Priority

    7. Due Date

    8. Original Estimate

    9. Remaining Estimate

    10. AssigneeLogged work

    Configurations