Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create solution-recommendations-perticket #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create solution-recommendations-perticket #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions _kpis/solution-recommendations-perticket
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
title: Number of solutions recommeded for the issue for the Ticket
layout: kpi
author: Pushparajan
---
The teams should own solutions for the defined problem. capturing the number of solutions the team experiement with before providing the ideal solution to the customer is important


## Formula
The total number of assignees can be determined through simple addition:
* N<sub>a</sub>: Number of recommended solutions / approaches

## Maturity Score
This is not a direct metric from the JIRA ticket process, a custom metric need to be defined and tracked for this purpose. It does not mean that there should be n number of PoCs before implementing a solution, yet, the number of innovative solution will be the gauge and will have to be defined by the tech leads this is a subjective metric