Alternative take: I have not met a serious craftsperson software engineer who did not deeply care about some KPIs. They might not have called them KPIs, but there were numbers they tracked constantly.
In the example of being asked what testing KPIs to tracked, why wouldn’t they include:
- Flake rate
- Test run time, a large component of CI lag
As much he might be correct about product development, in my experience, there are metrics that are early indicators of getting paid. Those metrics naturally become KPIs.
Comments
Alternative take: I have not met a serious craftsperson software engineer who did not deeply care about some KPIs. They might not have called them KPIs, but there were numbers they tracked constantly.
In the example of being asked what testing KPIs to tracked, why wouldn’t they include:
- Flake rate - Test run time, a large component of CI lag
Those are metrics, not KPIs
As much he might be correct about product development, in my experience, there are metrics that are early indicators of getting paid. Those metrics naturally become KPIs.
I've read it here and believe it: "KPIs are a psyop created by google to slow companies down" (in process, etc)
A rather one-dimensional view on the topic
The "fact" is an anecdote followed by an opinion.