Root Cause Analysis – True QA
Why Root Cause Analysis Matters in QA
Continuous improvement is the backbone of any effective Quality Assurance (QA) program. Regardless of the Software Delivery Life Cycle (SDLC) approach, Agile, Waterfall, or Iterative—organizations must continually refine their processes. One of the most powerful tools for this is Root Cause Analysis (RCA). However, here’s the catch: securing buy-in from the business side to invest in RCA can be challenging.
Organizations must realize that the insights and metrics RCA provides are essential for future success. Research (Berriault, 2012) and discussions at QUEST 2014 both highlight the importance of strong communication between QA and business teams. Shifting the focus to collaboration and understanding both sides’ needs leads to better outcomes for everyone.
The Real Value of RCA
RCA isn’t just about counting defects or assigning blame. It’s about tracking and identifying recurring issues so teams can develop real solutions that boost quality and speed. A solid RCA process impacts innovation, technology efficiency, and overall output. It’s not a quick fix—it’s a careful, data-driven approach that relies on teamwork and honest analysis.
Too often, organizations focus solely on surface-level metrics, such as defect counts or severity levels. This leads to short-term fixes:
- Hiring more staff
- Pushing overtime
- Delaying real solutions to future releases
These options are easy to implement but expensive and ineffective in the long run. They don’t address the root problems and can damage ROI. To truly improve, you need to define the data you need before starting your RCA.
Rethinking “Defects” as “Saves”
Instead of focusing on defects, consider tracking “saves”—any situation that threatens a project’s ability to deliver as expected. This could be anything from a coding bug to a printer jam. Don’t panic if the number of saves goes up; it doesn’t mean your product is flawed. Instead, it means you’re capturing valuable data that can drive improvement.
Think of your RCA as a car’s computer system: constantly monitoring and reporting issues so you can fix them before they become major problems.
RCA: More Than Just Numbers
The real power of RCA lies in the analysis, not just in collecting numbers. Good RCA removes blame from the equation and focuses on fixing processes, rather than individuals. It’s about asking the right questions and gathering the right data, starting early in the SDLC and continuing throughout.
Attach a dollar value to your saves. Track the time spent investigating, fixing, and retesting issues. Use this data to show the financial impact of recurring problems—and the savings from effective solutions.
Practical Example: The “Why-Why” Analysis
Let’s say a coding issue deletes all reports:
- Why? The developer coded the module incorrectly.
- Why? They didn’t follow coding standards.
- Why? The developer was new and had not received proper training.
- Why? No one confirmed they understood the standards.
- Why? There was no time for onboarding.
The root cause? Poor training procedures. Now, you can track how often this happens, calculate the annual cost, and justify a simple, cost-effective solution—like a job shadowing session for new hires.
Make RCA a Habit, Not an Afterthought
Root Cause Analysis is a powerful and adaptable tool that can enhance any development process. By focusing on process—not people—you’ll foster a culture of continuous improvement and true quality assurance.
Ready to take your QA program to the next level?
If you want to learn more about applying RCA in your organization, check out my book, Root Cause Analysis: True QA, or reach out to discuss how we can help you build a smarter, more effective QA process.
Contact: jberriault@berriaultandassociates.com |
Contact: jberriault@berriaultandassociates.com |
WORKS CITED
Berriault, J. (2012, September 16). Breaking down the root cause for the knowledge gap between testing and business. Retrieved February 5, 2013, from Athabasca Library: http://dtpr.lib.athabascau.ca/action/download.php?filename=mba-12/open/BerriaultJeremy.pdf
TED . (2009). How great leaders inspire action .
Slack, N., Chambers, S., & Johnston, R. (2010). Operations Management (6th edition ed.). Edinborough Gate: Prentice-Hall.
"I help create ecosystems that become legacies.”
- Jeremy Berriault
Quick Links
Hours of Operation
Monday - Friday
9 am to 5 pm
Saturday - Sunday
Closed