Control Quality

The process of checking and documenting the outcomes of quality activities to evaluate performance and confirm that deliverables are complete, accurate, and meet customer needs.

Key Points

  • Focuses on inspecting work and deliverables to verify they meet defined quality criteria.
  • Relies on tools such as inspections, checklists, sampling, control charts, and testing.
  • Generates results like quality measurements, confirmed deliverables, defect logs, and potential change requests.
  • Occurs during project execution and is distinct from planning quality and improving process design.

Example

On a software project, the team runs system tests, records defects in a log, analyzes a control chart for defect trends, and re-tests fixes. Once a feature passes all acceptance criteria, the team marks the deliverable as confirmed and ready for stakeholder review.

PMP Example Question

During execution, the team performs inspections, documents test results, and compares them against acceptance criteria to ensure the product is correct. Which process are they performing?

  1. Plan Quality Management
  2. Manage Quality
  3. Control Quality
  4. Validate Scope

Correct Answer: C — Control Quality

Explanation: Control Quality is about measuring, inspecting, and recording results to verify that deliverables meet quality requirements. Manage Quality focuses on process and quality assurance, while Validate Scope is about formal acceptance by the customer.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course