There’s an interesting discussion going on in the testing community, where someone has asked what Testing Metrics to track. It’s quite common to have this question in mind when you are approaching Testing from a new perspective or as a person starting Testing afresh.
Metrics are, and should be, designed keeping in mind the people that they serve. As you can see at your work, your Product Owner will be tracking a different set of Metrics at the product level, whereas your Test Manager will be tracking a different set of metrics, probably related to bugs filed, test productivity, and so on.
From a test function perspective, it’s important to have a ‘mission’ statement or a well-written goal. Each word in that statement (or) goal is important, and would point to the metrics that should be tracked, which in turn leads to actions that should be taken related to each of those metrics.
Carefully designing the goal statement and the metrics will lead to tracking the right things that you consider important towards better product Quality.
If you have any questions about how to design better metrics or about Software Quality, or If your organisation is looking for a Testing Strategist, please feel free to contact me. I would be glad to help!
Pingback: Testing Metrics related to Supply Chain – Test Musings, by Venkat Ramakrishnan