7.2.5: Step 5 - Create a Defect Log or QA Tracker

Project Planning and Control - A Practicum · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    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.

    This page titled 7.2.5: Step 5 - Create a Defect Log or QA Tracker was last modified on Wed, 02 Sep 2026 04:01:37 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Sukhjit "Bob" Singh.