Skip to main content
Workforce LibreTexts

7.2.4: Step 4 - Define QA Criteria for Key Deliverables

  • Page ID
    52311
  • \( \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

    Quality control is not just about fixing what’s broken—it’s about ensuring that deliverables meet predefined expectations the first time.

    This step helps you define the standards and criteria by which key deliverables will be assessed during execution. These criteria protect the project from:

    • Stakeholder dissatisfaction

    • Excessive rework

    • Delayed approvals

    • Low-impact or off-target outcomes

    You’re now designing the definition of “done” for each critical item.

    🧱 Step-by-Step Instructions

    🔹 1. Identify the Deliverables to Be Evaluated for Quality

    Focus on stakeholder-facing or mission-critical deliverables.

    📘 Examples:

    • “Final Training Manual”

    • “Workflow Design Diagrams”

    • “Stakeholder Onboarding Presentation”

    • “Pilot System Configuration”

    • “QA Test Plan”

    Avoid tracking trivial internal drafts. Focus on what would require approval, acceptance, or sign-off.

    🔹 2. Build a QA Acceptance Criteria Table

    Create a table for quality assurance with the following fields:

    Column Description
    Deliverable Name Match WBS or scope language
    Owner / Lead Who is responsible for quality delivery
    Quality Criteria Clear, measurable, and relevant expectations
    QA Method How will quality be assessed (review, test, approval, etc.)
    Reviewer / Approver Role or title of the person signing off
    Due Date When the review or acceptance is expected
    Status Pending, Accepted, Rework Needed
    Notes / Exceptions Issues, feedback, or improvement required

    🔹 3. Define SMART Quality Criteria

    Use specific, measurable, actionable standards—no vague phrases like “should be professional.”

    📘 Examples of Effective QA Criteria:

    Deliverable Sample QA Criteria
    Training Manual 100% of core modules covered, no broken links, uses UCMS branding
    Pilot Workflow All steps verified by SME, matches system behavior, legible in print
    Test Plan Includes pass/fail for each feature, aligned with requirements spec, reviewed by QA lead

    📘 Tip: Ask yourself, “What would cause this to be rejected by a client?” and use that to reverse-engineer your criteria.

    🔹 4. Determine QA Method and Review Process

    Decide how quality will be checked:

    • Internal peer review

    • Client stakeholder sign-off

    • Automated or manual testing

    • Demo or walkthrough validation

    • Scorecard / Rubric-based review

    📘 Example:

    “Workflow Diagrams will be peer-reviewed by Systems Analyst, then submitted for stakeholder sign-off. Final approval due 5 business days before Go-Live.”

    🔹 5. Assign Ownership and Reviewer Roles

    Assign clear accountability:

    • Owner: the person/team who must meet the criteria

    • Reviewer: the person/team who must verify and sign off

    • These may be different, especially in QA workflows

    📘 Tip: Include title, not just names (e.g., “Training Lead” or “Client SME”) for flexibility.

    🔹 6. Example QA Criteria Table

    Deliverable Owner QA Criteria QA Method Reviewer Due Date Status Notes
    Stakeholder Training Deck Instructional Lead Covers all modules, branded, <15 typos, approved examples Manual review + client sign-off Sponsor / Training SME Apr 14 Pending SME sign-off scheduled Apr 12
    Workflow Maps BA Includes all decision paths, print-ready, stakeholder-reviewed Peer review + walkthrough Product Owner Apr 8 In Review Requires version control stamp

    🧠 Why This Step Matters

    Too often, teams focus only on delivery and not on acceptance. Without pre-agreed quality standards:

    • You waste time chasing unclear approvals

    • Sponsors lose trust in your work

    • “Done” becomes subjective

    This step:

    • Clarifies expectations early

    • Builds trust through transparency

    • Prevents rework by aligning “quality” to shared definitions


    ✅ Once you’ve defined QA criteria for your critical deliverables, you’re ready to track performance in real time.


    7.2.4: Step 4 - Define QA Criteria for Key Deliverables is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?