Versions Compared

Old Version 28

changes.mady.by.user Roopa P

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.

...

Expand
titleWhat are the steps to set up Repo tools such as GitHub, GitLab, Bitbucket, Azure Repo, etc.?

Kindly refer the document Repo Tool Connection / Repo Tool Configuration.

Expand
titleWhy can't I see the assignee in Capacity Screen/Iteration/Daily Standup?

Make sure to enable the Individual KPI Toggle while creating a project to view the assignee details.

Project Configurations

Expand
titleHow to setup a project and configure a connection in KnowHOW?

Please refer to the link for on how to create and configure a project Configure Project & Connection

...

Expand
titleWhat should I do if I encounter a processor failure?

  • To troubleshoot the issues, it is recommended to verify the credentials in the connection tab. If the credentials are expired, you will need to update them in the connection tab to resolve the issue. Additionally, cleaning the data and rerunning the processor can also help in troubleshooting the problem.

  • If you are using DOJO Jira, make sure to select Bearer Token authentication and add your Personal Access Token (PAT) in the connection tab. Don't forget to validate the connection.

Generic KPI Question

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

Expand
titleWhat If I delete some stories in JIRA. Does it is still visible in PSknowHOW KPIs Dashboard?

Clean up the DB and prefetch item

Expand
titleWhat is the next option if client is not following Agile?

Kanban

Expand

Kanban

Speed KPI

Quality KPI

Expand
titleWhat are the likely scenarios when "no parent" stories are linked to defects in client environment?

Those defects will show up on Created vs Resolved defects KPI (if sprint is linked to the defects) and Defects Without Story Link (sprint is not mandatory) kpis.

...

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 

Expand
titleWhy am I not getting the correct data on the Wastage KPI?

  • There are two configuration options: Blocked issue and Include flagged issue. Make sure to select one of these options.

  • Update the mapping for "Status to Signify queue" (e.g. Ready for Testing, Code Review).

Expand
titleThe end date of the sprint does not match with the Jira sprint end date.

  • Some projects have a time zone difference in Jira, causing a 5-hour variation in the end dates.

Expand
titleWhat steps should I take if an active sprint is not visible in Iteration Board of KnowHOW?

  • If you encounter an active sprint that is not visible in KnowhOW, consider any recent changes in Jira teams or board configurations, as well as any alterations in team assignments. Ensure that updates regarding board names, teams, or any other relevant changes are reflected accurately in KnowhOW configuration

Release Board

DORA

Developer KPI

...