Skip to main content
Workforce LibreTexts

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{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

     

    🎯 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.

     


    7.2.5: Step 5 - Create a Defect Log or QA Tracker is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?