Are you looking for a simple, meaningful approach to gather and report defect metrics? Want to make your project defects more visible? Wondering how to report defects to management and show value? With an ever-increasing demand to show the business value of your testing, David Bialek explores a simple step-by-step method for metric management of issues.
This approach was developed and refined continuously to make software defects more visible as well as to analyze the findings to show the difference testing makes. Beginning with your bug list, learn root cause analysis, defect resolution, and how to plan and implement a meaningful metrics practice.
Explore the successes and failures of the metrics process and see how to move from the concept of metrics to measurement becoming a valued part of your project and test planning activities. Appropriate metrics demonstrate the importance of your team’s efforts and provide a key indicator of project and organizational health.
Join David in this metrics discussion and take back ideas to implement metrics for your team and management.
- Importance Defect Identification / Prioritization
- Business Buy-in
- Beyond bug scrubs
- Create Defect Root Cause categories
- Create Defect Resolution Reasons
- Analysis of Root Cause & Resolutions to create actionable items
- Understanding of how to use defect data to show the value of QA
- Learning from planning and implementing a metrics practice
Manager of QA Engineering, American Greetings
David is responsible for directing the quality assurance effort for all software development. During his seventeen year IT career, he was a QA consultant for Compuware and senior QA/BA with the Regional Income Tax Agency. David is currently on the board of the Northern Ohio Software Quality Assurance Association and served on the board for the SID Network of Ohio. David lives in Ohio with his wife Kimberly and their two children.
During the webinar, some questions came in that we were unable to get to, David has answered them here…
Muhammad: How to meter performance and security bugs?
David: Performance bugs and Security issues can be reported using the same method as presented. But each will have specific root causes and resolution reason categories that would need to be created in order to track effectively.
Marcelo: First, thanks for the presentation, i found it really useful. My project has 2 different fronts. Delivery team is Agile methodology, and the support team does a Kanban methodology. I’m having the issue that many of the “prod issues” are more of a “request” rather than an actual issue.
David: (If I understand the question correctly) Frequently production bugs can be new requirements/requests. I would change the disposition of the issue to a feature/story/requirement instead of a bug.
Marcelo: Is there any way/tool/thing that can have into account both methodologies at the same time? Is really hard to track metrics this way and requires a lot of manual, thoughtful filtering to get a realistic number.
David: Many tools exist that are methodology agnostic and provide the ability to create custom issue types and workflows. I would start with a search of products for issue tracking
Valentin: Do you use some tools which automatically collect, analyze and report on quality metrics?
David: Spoke about Qlikview /data warehouse, Jira for issue tracking and workflows.
Udhayasree: I would also like to get the defect metrics report, is there a easy way to pull defect metrics in TFS.
David: I am not familiar with TFS to offer an answer on this but I would start here: https://docs.microsoft.com/en-us/vsts/report/dashboards/overview
Jessica: • If someone is against tracking qa metrics, what arguments would you use to convince them otherwise?
David: In my opinion, an effective way of showing the value of testing is done using defect metrics. It provides us the ability to track the effectiveness of our testing, the fragility of the code base and is a measure of the strength of your STLC.