PSKnowHOW - Supported Ways of Working

The purpose of this document is to capture the best practices for KnowHOW KPIs.

The purpose of this document is to provide a well-defined specification for Jira configuration, ensuring the availability of data needed to calculate the KPIs in KnowHOW. It enables a Support analyst to accurately assess whether a team's configuration or requested customization is "out of compliance" and should be rejected.

Segment	KnowHOW KPI	Best practices for KnowHOW integration	Minimal required configuration in JIRA
Speed	Sprint Velocity	Estimation completed on story points before start of iteration Story point baselining should be practiced (i.e. start with base story with story point 1, and compare rest other stories with base story to estimate)	Estimation field in Jira story should be only “Story Point”. Any other estimation field on standard issuetype (i.e. Story etc) should be avoided. Sprint should be added in standard issuetype (i.e. Story)
	Commitment Reliability	Avoid scope change Each planned story must have Sprint value set before start of sprint.	Nothing additional
	Sprint Predictability	Avoid scope change Each planned story must have Sprint value set before start of sprint.	Nothing additional
	Issue Count	None	Nothing additional
	Sprint Capacity Utilization	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be captured on sub-task level Original estimate should filled in each sub-task before start of sprint Time spent should captured before each end of the day during sprint execution	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be added only on sub-task level
	Code Build Time	Integration with CI/CD, Repo tools	Nothing additional
	Scope Churn	Estimation planning on story points Sprint tagging to the issues before sprint start	Story point should be added for estimation in standard issuetype (i.e. Story) Sprint should be added in standard issuetype (i.e. Story)
	Build Frequency	Integration with CI/CD tools	Nothing additional Jira integration with one of the CI/CD tool (Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD)
Quality	Defect Injection Rate	All logged defects must get linked with stories planned in sprint.	Provision to mandate that, if defect created then must get linked with story
	First Time Pass Rate	Run time status update All logged defects must get linked with stories planned in sprint.	Provision to mandate that, if defect created then must get linked with story
	Defect Density	All logged defects must get linked with stories planned in sprint. Root cause field is updated	Provision to mandate that, if defect created then must get linked with story Root cause field is configured in defects
	Defect Seepage Rate	Run time status update All logged defects must get linked with stories planned in sprint. Escaped defect field is configured	Provision to mandate that, if defect created then must get linked with story Escaped defect field is configured in defects
	Defect Removal Efficiency	Defects are planned in sprint	Nothing additional
	Defect Rejection Rate	Defects are planned in sprint	Nothing additional
	Defect Count By Priority	Link all defects with the stories in the sprint by priority	Nothing additional
	Defect Count By RCA	Link all defects with the stories in the sprint by root cause	Root cause field is configured in defects
	Created vs Resolved Defects	Defects are planned in sprint	Nothing additional
	Regression Automation Coverage	In test management tool, select regression, automation options and complete traceability by mapping with story	Nothing Additional
	In-Sprint Automation Coverage	In test management tool, select regression, automation options and complete traceability by mapping with story	Nothing Additional
	Unit Test Coverage	Integration with SonarQube
	Sonar Violations	Integration with SonarQube
	Tech Debt - Sonar Maintainability	Integration with SonarQube
	Sonar Code Quality	Integration with SonarQube
	Test Execution and pass percentage	Integration with test management tool	Nothing additional
Value	Release Frequency	Link Jira issues tagged with the fix version The release should have a start and end date	Nothing additional Jira integration with one of the CI/CD tool (Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD) Check the provision to mandate release start and end date when added fix version.
	Value Delivery (Cost of Delay)	Epic (considered as feature in JIRA) should have the fields User-Business Value, Time Criticality, Risk Reduction and Opportunity Enablement	Epic should have User-Business Value, Time Criticality, Risk Reduction and Opportunity Enablement fields configured
	PI Predictability	Planned and Actual value should be added in the Epic (considered as feature in JIRA)	Epic should have Planned Value and Actual Value fields configured
Iteration	Iteration Commitment	Estimation planning on story points Before the start of the sprint, all items should have an estimate and added to the sprint	Story point should be added for estimation in standard issuetype (i.e. Story)
	Planned Work Status	The due date must be added to the issues	Duedate should be configured in JIRA
	Quality Status	All logged defects must get linked with stories planned in sprint.	Nothing additional
	Dev Completion Status	Dev due date must be added to the issues	Dev duedate should be configured in JIRA
	Work Remaining	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be captured on sub-task level Original estimate should filled in each sub-task before start of sprint Time spent should captured before each end of the day during sprint execution	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be added only on sub-task level
	Defect Count By Status	All logged defects must get linked with stories planned in sprint.	Nothing additional
	Defect Count By RCA	Link all defects with the stories in the sprint by root cause	Root cause field is configured in defects
	Unplanned Work Status	The due date must be added to the issues	Duedate should be configured in JIRA
	Defect Count By Priority	Link all defects with the stories in the sprint by priority	Nothing additional
	Closure Possible Today	The due date must be added to the issues Run time status update Time spent should captured before each end of the day during sprint execution	Duedate should be configured in JIRA Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be added only on sub-task level
	Issues Likely to Spill	The due date must be added to the issues	Duedate should be configured in JIRA
	Wastage	Runtime status update	Nothing additional
	First-Time Pass Rate	Run time status update All logged defects must get linked with stories planned in sprint.	Provision to mandate that, if defect created then must get linked with story
	Risk and Dependencies	Link all risk and dependencies in a sprint	Nothing additional
	Estimation Hygiene	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be captured on sub-task level Original estimate should filled in each sub-task before start of sprint Time spent should captured before each end of the day during sprint execution	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be added only on sub-task level
	Estimate vs Actual	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be captured on sub-task level Original estimate should filled in each sub-task before start of sprint Time spent should captured before each end of the day during sprint execution	Time tracking (Original estimate, Remaining Estimate, Time Spent) field should be added only on sub-task level
	Iteration Burnup	Due date in all issues in a sprint	Nothing additional
	Daily Standup	None	Nothing Additional
Developer	Mean Time to Merge	Integration with the Repo tool	Nothing additional
	PIckup Time	Integration with the Repo tool	Nothing additional
	PR Size	Integration with the Repo tool	Nothing additional
	Rework Rate	Integration with the Repo tool	Nothing additional
	Check-Ins & Merge Requests	Integration with the Repo tool	Nothing additional
Release	Release Burnup	Link all issues with the release The release should have a start and end date Dev duedate & Due date must be added to issues Estimation planning on story points	Dev duedate and Due date should be configured in JIRA
	Release Plan	Link all issues with the release The release should have a start and end date Dev duedate & Due date must be added to issues Estimation planning on story points	Dev duedate and Due date should be configured in JIRA
	Release Progress	Link all issues with the release The release should have a start and end date	Nothing Additional
	Defect Count By Status	Link all defects with the release	Nothing Additional
	Defect Count By Assignee	Link all defects with the release Defects should be assigned	Nothing Additional
	Defect Count By RCA	Link all defects with the release Root cause field is updated	Root case field should configured in JIRA
	Defect Count By Priority	Link all defects with the release Add priority	Nothing Additional
	Defect By Testing Phase	Link all defects with the release Add Testing Phase	Configure testing phase in Defects
	Epic Progress	Runtime status update of epic in JIRA	Nothing Additional
DORA	Change Failure Rate	Integration with the SCM tools	Nothing Additional Jira integration with one of the CI/CD tool (Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD)
	Deployment Frequency	Integration with the SCM tools	Nothing Additional
	Lead Time for Change	Integration with the SCM tools	Nothing Additional Jira integration with one of the CI/CD tool (Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD) Check the provision to mandate release start and end date when added fix version.
	Mean Time To Recover	Create and close Incident on run time in JIRA	Configure Incident issuetype in JIRA
Backlog	Backlog Readiness	Estimation completed on story points before start of iteration Story point baselining should be practiced (i.e. start with base story with story point 1, and compare rest other stories with base story to estimate)	Estimation field in Jira story should be only “Story Point”. Any other estimation field on standard issuetype (i.e. Story etc) should be avoided. Sprint should be added in standard issuetype (i.e. Story)
	Iteration Readiness	None	Nothing Additional
	Production Defects Ageing	Link all defects with the release Add Testing Phase	Configure testing phase in Defects
	Defect Reopen Rate	None	Reopen transition and status should configured in defects from “In Testing”, “Ready for testing”, In UAT & Closed
	Issue Without Story Link	?	?
	Refinement Rejection Rate	None	Nothing Additional
	Flow Efficiency	None	Nothing Additional
	Lead Time	Runtime status update in JIRA All workflow statuses must get aligned with columns in Agile board.	Nothing Additional During Jira board setup, all workflow statuses must get aligned with columns in Agile board.
	Flow Distribution	None	Nothing Additional
	Flow Load	None	Nothing Additional
	Cycle Time	None	Nothing Additional One status should set for DOR One status should set for DOD One status in Jira should set for LIVE OR Jira integration with one of the CI/CD tool (Jenkins, Bamboo, Github Action, Azure Pipeline, Teamcity, Argo CD)
	Epic Progress	Runtime status update in JIRA	Nothing Additional
	Backlog Count By Status	None	Nothing Additional
	Backlog Count By Issue Type	None	Nothing Additional
	Defect Count By Type	None	Nothing Additional