Bottlenecks are the primary driving factors for increased risk in testing. One way to identify bottlenecks is by Metrics. A Metric is the key system for how you can gather information to prevent and breakthrough your bottlenecks. Adam stated,
“ A good metric can truly help you collect and understand information that can influence your business decisions.”
Don’t just measure for the sake of measuring. But how do we choose our Metrics? You must consider the health of your product and the health of your team. Does one person have a backlog of work that prevents someone else from doing their work?
Key Rules for Metrics Gathering:
Set up metrics and reporting early
Define your metrics – make sure they are processed and actionable
Data by itself can be dangerous – make sure the data tells a story
Key Takeaways in Sprint Metrics that your Team Can Use to Break Through Bottlenecks:
Defect Aging – Must have open communication between teams to track defects
Open defects categorization– Understanding categories for your defects can help you understand where you need to focus efforts to make sure delivery is on time
Velocity– Estimated effort vs. actual effort
Metrics can help drive learning and decisions to ensure that we stop being reactionary!
Key Takeaways on How to Save the Day:
Learn from your experiences
Understand the metrics that resonate with your team
Build reporting early
Take a look at the overall customer impact & uncover errors before customers report them
Focus on metrics before and after production
Rinse & repeat
Here’s a bonus sneak peek to our Q+A:
Q: How would you evaluate and communicate the value of QA to your broader organization?
A: In order to truly know if testing has a positive or negative affect on what is being released, you have to understand how the customers are seeing the product. Show test coverage and the validate that scenario. Prove your value in catching defects that would’ve been missed and would’ve been reported by the customers instead of QA.
Q: When does defect tracking become harmful?
A: When it is used as a punishment tool. It should be used as a learning tool.
A huge thanks to everyone who attended and, as always, let us know if there are any topics you would like for us to consider for future webinars by tweeting us at @QASymphony or emailing firstname.lastname@example.org.