Versions Compared

Key

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

...

Expand
titleHow to validate PSknowHOW KPI's dashboard data?

Go to your Jira server and select any sprint to validate as per your wish and then apply the JQL to fetch the data in Jira and compare the output with respect to KnowHOW dashboard data and start validating the data. . If after doing all this you still see the data gap b/w Jira server and KnowHOW server, you can raise a DOJOSupport Request.

...

Expand
titleWhy is there a mismatch in the data for defect injection KPIs?

Make sure that for Defect Injection Rate (DIR) KPI defects are tagged to stories, and those stories should be closed within the same sprint. Refer the doc for DIR KPI

Expand
titleHow is DIR and Defect Density calculated in KnowHOW?

Defect Injection Rate/Defect Density

NUMERATOR: If a defect is tagged to the story that is tagged to the sprint, it is considered

  • If a story spills, then defect will be considered in the sprint when story gets closed

  • Defects that were raised earlier/defects raised but not tagged to sprint will be considered

DENOMINATOR: All stories closed in the sprint (irrespective whether they had any defect)

EXCLUSION: Defect is raised tagged to the sprint but the corresponding story not tagged to sprint 

Value KPI

Iteration Board

Expand
titleWhat happen in Jira when we delete OR make some changes in Sprint. Does it still show deleted/changes made in the Sprint in PSknowHOW ?

If sprint is deleted, you want to clean up and re fetch the items.If there are changes like date modified, name modified, restart the collector and it will get updated in DB

...

Expand
titleIn the calculation of commitment reliability KPI, are issues that are completed, not completed, removed, or added during the sprint considered?

In Initial commitment it consider Completed issue, Issues not completed, minus scope added ,Plus scope removed.

Expand
titleHow is DIR and Defect Density calculated in Iteration Board "Quality Status KPI"

Iteration Dashboard

Defect Injection Rate/Defect Density

NUMERATOR: If a defect is tagged to the story that is tagged to the sprint & defect itself also tagged to sprint, it is considered

  • Defect needs to be created between start and end date of the sprint and tagged to the sprint

DENOMINATOR: Linked stories to the defects that are counted are considered (Closed story with or without defect, In progress story with defect)

EXCLUSIONS: If the defect is raised during sprint 'n' and tagged to sprint n+1 inspite of the story being tagged to sprint n, it will not be considered in any sprint 

Release Board

DORA

Developer KPI

...