The ultimate KPIs for software development?<\/p>\n
Here are the top 3 I feel are important:<\/p>\n
1. Defects from production – Severity and quantity.
\n– This should be the end goal that should matter.
\n– Most of the other quality KPIs like automation coverage % etc. are not the end goal,
\n– They are how good you are following ‘a process’, which may or may not achieve in the ultimate goal.<\/p>\n
2. Mean bug identification time
\n– Average time taken to report bugs after code commit.
\n– This does not mean just JIRA tickets raised as bugs, automation results showing failures giving feedback too are included.
\n– This will capture how quickly we are giving feedback on code changes, which is a significant part of driving costs down.<\/p>\n
3. Release cadence
\n– How quickly do we release a feature, starting from conceptualization till deployment into production.
\n– This should include all the lead time across all processes.
\n– The company that masters to speed this process will win, since they can adapt and change quickly looking at how customers respond.<\/p>\n
There can be many other KPIs, I personally want to care about only these 3.<\/p>\n
#RedefiningSoftwreQuality #DevOps #KPI #Automation<\/p>\n<\/div>