Defining the testing metrics that matter for your team is absolutely crucial in an agile environment, where testers have to keep up with rapid development cycles. While there are many schools of thought on this topic, I believe that you only need this basic rule to determine the testing metrics that matter most:
The testing metrics that matter are the ones that directly impact the success of your business.
Seems simple, right? That’s because it is! And yet, many testing teams get caught up in the details of different requirements and defects they think are important to track, that might not really be that important at all.
Let’s take a free product like a Facebook for example. Arguably, the most crucial element to Facebook’s success is that the site never goes down, which means their testers must be focused on metrics surrounding the stability of the site. For a bank or financial institution, data protection and security are absolutely essential to their success, so this metric matters above all others. For a mobile app company, usability might be the most important metric the measure.
Every team must decide which metrics are going to most directly affect the bottom line of the business. The answer is different for every product. And yet, as every company works to determine the unique metrics that matter most, there is this one universal truth – the perception of the end user always impacts the success of your business. Testers must be constantly channeling the voice of the customer as they work, looking for ways to improve the product for the people who will ultimately be using it.
Finding the testing metrics that most directly impact the success of your business and the happiness of your customers is crucial for agile testers and development teams.