What sort of KPIs do you use on your engineering processes and infrastructure? Sprint Velocity, No of hotfixes, API response times, client bundle file size, etc, etc..
For further actions, you may consider blocking this person and/or reporting abuse
What sort of KPIs do you use on your engineering processes and infrastructure? Sprint Velocity, No of hotfixes, API response times, client bundle file size, etc, etc..
For further actions, you may consider blocking this person and/or reporting abuse
dev.to staff -
Archie -
Luxand.cloud -
Thomas Hansen -
Top comments (2)
I'm always nervous about perverse incentives that can come out of measuring software engineering too closely.
Response times and bundle size seem reasonable, but I'm also not sure how you measure improvement apples-to-apples against theoretical alternatives there.
I've always worked with small teams, so engineering KPIs haven't always offered more good than bad. I can imagine in a larger org, it could help.
Now that we're open source I could see us working community PRs merged as a KPI. Seems to generally incentivize smaller PRs, more contributors, and feature/bug-fix velocity.
Just a random memory: after your metric becomes a targrt, it is no longer a good metric.