Systems & data KPI (KPI proposed: Number of System/Master Related…
Systems & data KPI
KPI proposed: Number of System/Master Related Changes
How do we define / what do we mean by:
Is this KPI homogeneous?
Yes, we can compare it reasonably (one unit is similar to another in a different context)
No, not comparable in terms of:
Time: e.g. one change request takes 1 day or 6 weeks
Complexity / expertise: e.g. one more complex change request must be handled by a person with specific expertise
Know how not transferable
How to reflect diversity and non-comparability?
Provide comments / qualitative assessment? … to give context
Assign points, credits, weights? Time spent?
At what level is it to be measured?
Across a system?
Across only the part of the system where we're involved (i.e. subset)?
What is the scope?
SAP, Easy, Cost Model etc?
Frequency of measurement?
Data source for measurement
Is there one data source?
Who's going to measure it? How to ensure objectivity and integrity of data and unbiased approach?
Classification: e.g. on and off change requests (is it still one unit or a new one?)
At whose discretion is it measured? Can you be responsible for measuring your own KPIs?
How representative the KPI is of total effort? E.g. does it explain 50% of effort of the team?
Is the KPI in or out of our control? Can we influence it?
What does the KPI tell us?
Is it good / bad if the KPI is up or down?
Are there various ways for interpretation? (i.e. good, bad, neutral depending on the point of view)
Consistency over time? Is one unit now same as one unit five years ago?
Is this the right KPI?
What is the KPI supposed to capture?
Why having KPIs? What is this for?
Compare effort / productivity across teams? (i.e. comparing to others)
Provide historical comparison (i.e. comparing to ourselves?)
Who is this for? What decisions it's going to drive? What conclusions will be formed as a result?