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

First Time Pass Rate

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

    Percentage of tickets that passed QA with no return transition or any tagging to a specific configured status and no linkage of a defect.

    Calculation Logic

    First Time Pass Stories - Stories which are not having return transition or defect tagged.

    Total Stories - Complotted issues from sprint report.

    First Time Pass Rate - First Time Pass Stories/Total Stories.

    Note:

    1. Issue types configured under Issue Type Mapping - FTPR will be considered as stories.

    2. Exclusion parameters(defect priority, RCA) will work same like Quality board FTPR.

    Filters

    Filter by issue type

    Filter by Status

    Columns in Overlay Screen

    1. Issue Id

    2. Issue Description

    3. Issue Status

    4. Issue Type

    5. Size(story point/hours)

    6. Priority

    7. Due Date

    8. Original Estimate

    9. Remaining Estimate

    10. Assignee

    Configurations

    2. First time pass

    3. Linked Defect

    4. Defect Priority

    Configuration

    Processor Fields

    NA

    Mandatory fields

    • Issue type Mapping

      • Issue types to consider ‘Completed status eg; Story, Tech Story

    • Workflow Status Mapping

      • Status to identify completed issues eg; Closed ,Resolved,, Done , Live

    • Status for 'In Development' issues eg; Analysis, In Progress

    • Status to Identify In Testing Status