7.2.5: Step 5 - Create a Defect Log or QA Tracker
- Page ID
- 52312
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Purpose of This Step
Even with strong QA criteria, some deliverables will fall short. The Defect Log (or QA Tracker) is a structured tool that helps your team:
- Record issues or quality gaps
- Classify them by severity and impact
- Assign owners and track status
- Ensure issues are resolved, not forgotten
This tool transforms reactive fire-fighting into a repeatable quality assurance process.
Step-by-Step Instructions
1. Determine What You Will Track
You can use the log to track:
- Defects (e.g., functionality issues, typos, missing content)
- Quality gaps (e.g., missing acceptance criteria, vague documentation)
- Review comments (e.g., stakeholder feedback, peer review flags)
Tip: Focus only on issues that impact stakeholder expectations, milestone approval, or readiness. Don’t log every small internal preference or personal style edit.
2. Build the Tracker Structure
Use a table or spreadsheet with the following fields:
| Column | Description |
|---|---|
| Issue ID | Unique identifier (e.g., DEF-001) |
| Date Logged | When the issue was first recorded |
| Deliverable Name / WBS ID | Affected document, feature, or output |
| Description | Clear, factual summary of the issue |
| Severity | High / Medium / Low |
| Type | Content / Visual / Functional / Format / Other |
| Owner | Person/team responsible for fixing |
| Status | Open / In Progress / Resolved / Deferred |
| Resolution Date | When it was completed/fixed |
| Notes / Action Taken | Additional comments or resolution steps |
3. Define Severity Levels
Add a simple reference guide to help your team assess impact:
| Severity | Description |
|---|---|
| High | Critical issue blocks delivery, breaks core functionality, or violates a key acceptance criterion |
| Medium | Noticeable issue impacts quality, but not delivery; stakeholder may raise concern |
| Low | Cosmetic or minor error; fix recommended but not urgent |
Tip: You can add color codes for quick scanning (🔴 Red = High, 🟡 Yellow = Medium, 🟢 Green = Low)
4. Assign Ownership and Status Rules
Every item in the tracker should have:
- A clearly assigned fix owner
- A status field updated regularly (Open → In Progress → Resolved)
- A note if the item is deferred (i.e., intentionally left unresolved)
Tip: Assign QA owner to follow up weekly or at each milestone checkpoint.
5. Add Examples to Your Tracker
Sample Log Entries:
| ID | Date | Deliverable | Severity | Description | Owner | Status | Resolution Date | Notes |
|---|---|---|---|---|---|---|---|---|
| DEF-001 | Apr 10 | Workflow Diagrams | High | Missing alternate path for rejection loop | BA | In Progress | – | Flagged by SME |
| DEF-002 | Apr 11 | Stakeholder Slide Deck | Medium | 3 typos in section headers | Training Lead | Resolved | Apr 12 | Fixed in v2.1 |
| DEF-003 | Apr 11 | Test Plan | Low | Table formatting misaligned on page 3 | QA Lead | Deferred | – | Not client-facing |
6. Optional Enhancements
Add one or more of the following features:
- Filter or sort by deliverable for team reviews
- Charts showing open vs. closed items
- QA trend log over time (e.g., # of issues per milestone)
- “Escalation” flag for unresolved high-impact items
Why This Tool Matters
Without a defect log:
- Teams lose track of known issues
- Quality reviews become inconsistent
- Minor problems resurface in later phases
- Sponsors lose confidence in deliverables
With it, you ensure that quality isn’t just “checked”—it’s managed and improved.