-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the KpiAccelerator wiki!
The KpiAccelerator tool is designed to help engineering teams track their four post insightful KPIs. These are Lead Time, Number of Deployments, Successful Changes, and Time to Recovery.
The application calculates these values from three datasources. These are added and manged through the File -> Update KPI Data menu option. These data sources are Work, Deployments, and Incidents.
To Import Work go to File -> Update KPI Data -> Work. This will open a dialog box for you to select a CSV file to import. This file should be exported from TFS, Jira, or whatever. The CSV File must have the following columns:
- ID
- Title
- State
- Created Date
- Closed Date (can be left blank for work not yet completed)
The application will use this information to calculate it's various KPIs.
You should consider carefully the queries you use to export this data. First and foremost it should be consistent each time you update the data, however you will need to decide which Work Item lead time you are most interested in. A User Story is typically created when a Feature is refined and broken down, do you want to measure the Lead Time of the Feature or the Story? That will depend on your business case.
You can manage your deployments either through adding them manually or importing them. You can also delete deployments by highlighting the row and clicking the Delete key. Changes will not be saved until you click Save and Close.
To manually add a deployment simply enter the Date of the deployment and it's name (to help you identify it later). Pressing the Add button will insert it in the deployment table.
If you want to import your deployments from an external system you can do this with a CSV file. Click the Import button and select the file. The required fields are:
- ID
- Name
- State
- Closed Date
When importing the application will not import a deployment if there is already one at the exact same time. This is to avoid duplication.
You can track the incidents your team deals with using the Incidents tab.
There are two kinds of incidents ones caused by deployments and ones which arose on their own. To help with this you can optionally link an incident to a deployment however this is not required. If you link an incident to a deployment this will impact your Successful Change Kpi. Both kinds of incidents are measured for recovery time.
As with deployments you can select a row and click delete to remove it. There is no import functionality for incidents at this time.
More of an academic question than a technical one but I'll have a go. The State of DevOps report lists these three KPIs as key for measuring how highly performant a team is. The Lead Time wants to be low, the Success Rate high, the Number of Deployments High, and the Recovery Time low. You should continue to monitor your KPIs to ensure they're heading in the right direction. For more information I highly recommend you read The State of DevOps Report.