Which Software Metrics and Why?
ShriKant Vashishtha
![ShriKant Vashishtha]()
ShriKant Vashishtha
Agile Consultant | Author of “Agile Estimation Distilled” | Ex-Director at GlobalLogic, Xebia | Open-Source Contributor
With my last post, it is clear that metrics are important to tell you the transparent truth of software delivery. The question still remains - which metrics should I use and why?
Sometimes people just look for available or known set of metrics and then add more as and when they discover one.
With that it sounds like - they are trying to fit in those known set of metrics to any situation. Does that make sense?
Let’s go back to our analogy of metrics with health checkup. Do you congregate a set of tests and fit them in for any scenario? That doesn’t seem to work.
Agile Consultant | Author of “Agile Estimation Distilled” | Ex-Director at GlobalLogic, Xebia | Open-Source Contributor
8 年Andrew Depending on the person in question, concerns (goals) may be different. For VP Engineering for instance, certain engineering metrics may not be immediate focus. The whole idea of GQM is - depending on who you are, define your goals. Ask questions which if answered may satisfy your goals. In order to get answers of those questions look for measurements (metrics). So you see, I am not really adamant to use a particular set of metrics. Depending on your goals, identify what's more important for you and measure the same. Again, that doesn't mean every VP Engineering will have same goals as you have. So GQM for the same role but in different context may be different.