Process · Quality Risk Analysis
Prioritize risk before you prioritize tests.Six steps from stakeholder consensus to approved risk register.
Testing without a prioritized quality risk analysis is testing by politics. This six-step process produces a risk register with explicit stakeholder consensus, the basis for every downstream testing decision.
- Steps
- 6
- Output
- Prioritized register
- Compatible with
- FMEA, informal QA
Any test effort that cannot point to an agreed-upon list of risks is really a test effort that nobody has agreed upon.
Key takeaways
Four things to remember.
01
Start from stakeholders, not from features
Identify who cares about quality and commit them to participate. Without their ideas in the room, the register is yours alone to defend.
02
Pick the technique, then stick to it
FMEA, informal QA, or something in between, match the technique to the team. The wrong technique picked well is better than the right one applied inconsistently.
03
Capture incipient bugs as you go
The analysis surfaces bad requirements, design flaws, and missing specs. File them; do not let them wait for test execution.
04
Close the loop with configuration management
A quality risk analysis that is not under change control is a document that will drift. Check it in and require change requests to alter it.
Why this exists
The problem this process fixes.
When the schedule compresses (and it always compresses) the test team needs a defensible ordering of what to test first, what to test less, and what to cut. That ordering is the quality risk analysis.
These six steps produce that ordering. Every subsequent decision in the testing process (estimation, case design, execution sequencing, release criteria) traces back to the register built here.
The checklist
6 steps, in order.
- 1
Identify the key testing and quality stakeholders. Obtain stakeholder commitment to participate in a quality risk analysis.
- 2
Survey the key stakeholders about the techniques and methods for quality risks analysis. If appropriate, propose a technique. Obtain consensus on the technique and the method selected.
- 3
Gather ideas from the key stakeholders about the quality risks, the failure modes associated with those risks, the quality impact of such failures, and the priority of the risks. Identify the recommended action to mitigate each risk.
- 4
Report any incipient bugs identified in other project documents during the analysis, such as bad or missing requirements, design problems, and so forth.
- 5
Document the quality risks as appropriate for the technique used. Circulate the document to the stakeholders for approval. Iterate steps three, four, and five as necessary to finalize the quality risks, their priorities, and the recommended actions.
- 6
Check the quality risks analysis document(s) into the project library or configuration management system. Place the document under change control.
One more thing
The quality risk analysis is the single most-cited document in a healthy test program. Release criteria point back to it. Test estimates are justified by it. Change requests are re-prioritized against it. Treat it as load-bearing.
Take it with you
Download the piece you just read.
The library is free. Tell us who you are so we can send you updated versions. One form; this browser remembers you after that.
In the library
Pair this with.
Process · The Master Framework
Four phases, applied in order, every project.
The top-level testing process used on every engagement. Four phases contain twelve sub-processes, each of which is documented in its own checklist in this library.
Read →Process · Context Discovery
Learn the ground before you move it.
The first thing a test leader should do at a new organization is understand the context. These five steps keep you from proposing the wrong solution because you misread the problem.
Read →Process · Test Estimation
Estimate testing the way projects actually work.
Test estimates fail either because they skip the work breakdown or because they skip stakeholder buy-in. This process does both, in sequence, so the resulting schedule and budget survive contact with management.
Read →Process · Bug Reporting
Write bug reports developers act on.
A bug report is a sales document aimed at a developer. This is the ten-step sequence we use on every engagement to write reports that get fixed instead of dismissed.
Read →
Keep reading
Related reading
- Primer
Your First Test Cases: Designing Tests That Find Problems
A hands-on introduction to test design. Learn what goes into a test case, then use two classic techniques, equivalence partitioning and boundary value analysis, to test a sign-up form the way professionals do.
Read → - Primer
What Is Software Testing? A Plain-English Introduction
Software testing explained from the beginning: why every program has mistakes in it, what testers actually do all day, and the handful of ideas the whole profession is built on. No experience needed.
Read → - Primer
What Is Cybersecurity? The Ideas Behind Keeping Systems Safe
Cybersecurity explained from the beginning: what it protects, who it protects against, and the handful of ideas every security professional uses, from the CIA triad to defense in depth. No experience needed.
Read → - Primer
Testing a Website: A Beginner's Checklist
A practical checklist for testing a website before it launches: links and navigation, forms, browsers and devices, accessibility, speed, content, search basics, and security basics, with the free tools that make each check fast.
Read → - Primer
Staying Safe Online: Passwords, Sign-In, Phishing, and Updates
The everyday security habits that stop most attacks: strong unique passwords, multi-factor sign-in, spotting phishing, keeping devices updated, and sharing carefully. Written for students, families, and anyone starting out.
Read → - Primer
Security Testing Basics: Finding Weaknesses Before Attackers Do
An introduction to security testing for new testers and developers: thinking in threats, designing abuse cases, testing access control, the role of automated scanners and penetration tests, and the rules that keep security testing legal and ethical.
Read →
Practices
Where this leads
- QA & testingSoftware testing
Software quality consulting since 1994: we test the releases that matter, coach your team on the method, and measure how its testing matures.
Book a call →