Key Features Released

Iteration Dashboard

Additional KPIs have been added on the Iteration Dashboard. These KPIs together help in gauging the Iteration progress w.r.t Speed and Quality Iteration Dashboard Link.

1.Iteration Commitment KPI 

• The KPI shows 4 data points in terms of issue count and story points

  • Initial Commitment - No. of issues tagged to the iteration when it was started

  • Scoped added - No. of issues added during the iteration

  • Scope removed -  No. of issues removed during the iteration

  • Overall commitment is actually calculated as Initial commitment + Scope added - Scope removed

    • This is actually the issues tagged to the iteration when it is closed

2.Planned Work Status KPI 

• "Planned work Status" KPI is useful for teams that track each story against a due date within an iteration

• The KPI lets the user know that on any given day during the iteration

  • How many issues were planned to be completed

  • How many issues were actually completed

  • No. of days delay in the completed issues when compared to the due date

3.Unplanned work Status KPI 

• Contrary to Planned work status, this includes all issues without due dates

Note - Planned work completion and unplanned work status will be renamed and repurposed

4.Work Remaining KPI 

• This KPI considers all the issues which are not completed as on a given day within an iteration.

  • The remaining work is depicted in terms of "Issue count/Story Point," "Hours," and "Potential Delay."

  • Users can see the potential delay for all the stories which have a due date defined. 

  • Predicted completion date is also calculated for the pending issues

5.Quality Status KPI

• All key defect related KPIs are combined under Quality status

  • Story linked defects - All defects linked to stories

  • Unlinked defects - All defects other than the ones linked to stories

  • Defect Density and Defect Injection rate consider defects linked to stories equated against the story points and count of stories respectively.

6.Iteration Progress KPI 

• Iteration Burnup KPI Shows the cumulative actual progress against the overall scope of the iteration on daily basis.

7.Defect count by Status, RCA and Priority

• Defect count is segregated by RCA, Status and Priority.

• User can see the break up both for the total defects in an iteration and for the defects created after iteration start date.

8.Iteration Wastage 

• Iteration Wastage KPI considers the blocked and wait time that falls within a particular iteration .

  • An issue that is blocked for 24 hours in Jira is considered as 8 hours blocked 

  • Based on the configurations, users can chose to consider flagged issues also as Blocked.

9.First Time Pass Rate KPI 

• FTPR KPI is similar to the KPI on Quality dashboard and considers all stories which either have a defect linked or have transitioned through a configured status

  • Exclusion parameters: Rejected Resolution, Rejected Status, Priority, RCA.

10. Dev Completion Status KPI

• Similar to "Planned work Status" KPI, Dev completion status is useful for teams that track each story against a dev due date within an iteration

  • The KPI lets the user know that on any given day during the iteration

    • How many issues were planned to be dev completed

    • How many issues were actually dev completed

    • No. of days delay in the dev completed issues when compared to the due date.

11. Issue Likely to Spill KPI

• Issue Likely to Spill KPI: Spills are determined if Predicted Completion Date (PCD) exceeds Iteration end date.

12. Closure Possible KPI

• Closure Possible KPI: Issues with Predicted Completion Date (PCD) on or before the current day are considered possible closures.

Usability Enhancements

KPI Overlay experience on Iteration Dashboard

• Users can now customize the table view by adding/removing columns in the overlay 

• Users can sort/filter/reorder the columns.

  • The default sorting is on Assignee followed by Due date (wherever applicable).

• Fixed Table Header: The KPI overlay table header remains fixed when scrolling.

User can tag comments to each KPI for a project

Introduced new comments feature on KnowHOW, specifically designed to help users save a text field for saving comments per KPI in each project/sprint. This feature enables users to save notes and reference them in the future.

User can see all the trend data on Hover giving him/her the ability to easily compare the trend

Seamless integration between KnowHOW & JIRA

• For Speed, Quality and Value KPIs, user can see the Jira data by issue ID and navigate directly to Jira tool from KnowHOW.

  • A Modal Window is available to see sprint wise data on scrum dashboard and date wise on Kanban dashboard. This capability can be used for all hierarchy levels.

Backlog Dashboard 

• Defect Reopen Rate Backlog Dashboard Link

  • Defect Reopen Rate: Measures the number of reopened defects out of the total defects raised  KPI includes.
    1. Number of defects reopened.
    2. Reopened defects as a percentage of total defects raised.
    3. Average time to reopen: Calculates the average duration between the last closed date and the reopen date.

• Refinement Rejection Rate

  • Refinement Rejection Rate measures the percentage of rejected stories during refinement. for the last 5 weeks

  • To take benefit from the KPI users are required to identify three status in the workflow that signify that issues are "Ready for Refinement" OR "Accepted in Refinement" OR "Rejected in Refinement".

• Flow Load and Distribution KPI
  

  • Flow Distribution KPI evaluates the counts of each issue type that is open in the backlog over a specified period.

  • The dataset includes issues that have been open within the last 12 months.

  • Flow KPI indicates the number of issues currently in the backlog.

  • Backlog considers all open issues that are either tagged to Backlog or any future iteration. It excludes the issues tagged to active sprint on a given day

  • This KPI emphasizes limiting work in progress to maintain a fast flow of issues.

  • The X-axis represents the months, and the Y-axis  represents counts allowing you to track the backlog status over time.

• Backlog Readiness Efficiency KPI

  • Backlog Readiness Efficiency KPI: Measures backlog readiness based on ready Product Backlog items.

  • Determines if enough backlog items are available to be picked up in the upcoming iterations by equating the refined backlog size with the average velocity of past iterations

  • Calculates average time for Backlog items to be ready.

Release Dashboard 

• Release Defect KPI:  The KPI shows the breakdown of all defects within an iteration by:

  • Status

  • Priority

  • Assignee

  • RCA

• Release Burnup KPI 

  • Tracks progress of a release based on cumulative count of closed issues  

  • It highlights cumulative scope added/removed along with a breakup for each day 

• Release Progress KPI 

  • Release Progress KPI introduced: Tracks the count of issues in different stages: To Do, In Progress, and Done.

  • Based on the size of issues count & Story Point.

  • Filters show Issue type Assignee and Priority.

KnowHOW Landing page

Enhanced the UI of the KnowHOW Landing page by displaying all the current dashboard categories in the left navigation. The left navigation bar now displays the following dashboard categories in the given order.

• My KnowHOW

  • Speed

  • Quality

  • Value

  • KPI Maturity

  • Iteration

  • Backlog

  • User has the ability to do 6 selections for any level of hierarchy. For e.g. User can select 6 projects, portfolio's etc.

Feature to push KPI data by user

• Since every tool may not be integrated, this feature provides a functionality to push data through exposed APIs to populate data for KPIs.

  • It is being rolled out for Build tools so now the user can push data for KPIs like

    • Code Build time

    • Change failure data

    • Deployment frequency

  • Superadmin or Project Admin user can create a token for an existing project and use the API to push data to populate KPIs and projects wise data in saved in build details collection as per the specified format.

Maturity wheel enhancement

• User can see the maturity level only of Categories & drill down to see the maturity level of KPIs under category with all KPIs that have a maturity score and level associated with it.

• Maturity Score and Level Display: The maturity score and its corresponding level are now shown together in Speed, Quality, Value KPI.

Configuration of authentication types and Tool Connections 

• Superadmin user has the ability to enable/disable any type of login & authentication mechanism.

  • Unit Test KPI single select dropdown has been made configurable now.

Configuration Enhancements

• Jira Processor enhancements

  • Jira project configuration can now be done based on Board Name associated with a Jira project in addition to the JQL option.

• Jira KPI configurations enhancements

  • Users can identify fields required for a specific KPI configuration and can use this feature to avoid mistakes while configuration and gain understanding of KPI configurations without relying on KnowHOW roll-out team.

New Tools Support

• X-Ray tool integration

  • X-ray (Jira plugin) for test management can now be integrated with KnowHOW to get In-sprint automation, regression automation and Test without story link KPIs.

  • All Jira test management plugins (X-Ray or Zephyr squad) can now be configured through a common user interface.

• GitHub Action

  • Introducing the Git Hub Actions Build & Deployment Tool processor.

  • This new processor enables streamlined build and deployment processes using GitHub Actions.

  • The processor integrates seamlessly with GitHub repositories, allowing for efficient code management and version control.

Quality KPI Enhancements

Scrum QUALITY KPIs Link

1. First Time Pass Rate KPI 

   • The total number of stories considered for the First Time Pass Rate (FTPR) will now be based on the completed issues in the sprint report.

   • Issue types will now be mapped to stories to provide a more comprehensive view of the types of issues being tracked and resolved during the sprint.

   • Exclusion parameters for eg: Resolution type for Rejected, Rejected Status, Priority, RCA.

2. Defect Density and Defect Injection rate KPI now have Exclusion parameters for eg: Resolution type for Rejected ,Rejected Status, Priority ,RCA.

   • Unlinked Defects: Defects tagged to the sprint but not linked to a story will now be included in the Unlinked Defects KP.

   • DIR (Defects to Issues Ratio): DIR will be calculated as the number of linked defects divided by the number of  stories from the Sprint Report.

3. Created Vs Resolved KPI  

   • Created vs Resolved KPI consider all defect issue types mentioned in our mappings, including subtask defects, whether they are linked or unlinked.

   • The KPI will display 2 views for Created vs resolved.

     • One view will show all defects that have been tagged.

     • Second view will only show defects that were tagged after the start of the Sprint.

Speed KPI Enhancements

Scrum SPEED KPIs Link

1. Average velocity along with Sprint Velocity KPI 

• 'Last 5 sprints average' displayed on the graph for comparison with actual velocity of each sprint.

2.Commitment Reliability KPI 

• Introducing two new views to the Commitment Reliability feature.

• Users can now track commitment reliability based on the initial scope of work planned during iteration planning.

• Users can continue to track commitment reliability based on scope changes and updated count/size of issues.

• The new trend line represents commitment reliability based on the initial scope.

• Filter options include Initial Commitment (Issue Count), Initial Commitment (Story Point), Final Scope (Issue Count), and Final Scope (Story Point).

1. Story Count KPI 

• Story Count has been renamed to "Issue Count".

• The field name in mappings has been updated to "Issue Count" KPI Issue type.

• Two radio buttons have been added to the widget.

  • Story count option displays the count of stories.

  • Total Count option displays the count of issues based on the issue type mapping configuration.

• Hovering over the widget will show a breakdown of the count by each issue type.

Jira Template Configuration

• Added a JIRA Configuration Template dropdown field to select a template for mapping on the JIRA configuration screen.

  • The selected template will be maintained on the field mapping screen post running the JIRA processor.

  • If the user manually changes the mapping on the field mapping screen and saves it, the initially selected template will change to "Custom template" on the edit configuration screen, and the template dropdown will be frozen to "Custom template".

  • The available template options are DOJO SAFe Template, DOJO Agile Template (Default selection), and DOJO Studio Template.

 Azure Board

• Iteration dashboard will now work for Azure Boards

• The Iteration Board KPIs now provide insights and metrics for both active and closed sprints.

• Users can now track and analyze sprint details using the Iteration Board KPIs.

Capacity Table

• Happiness Index KPI

  • Happiness Index KPI introduced.

  • Happiness Index measures and analyzes the happiness and morale of team members.

  • Happiness Index displayed on the Y-axis rating.

  • Sprints tracked on the X-axis.