PMP Quality Questions: Acceptance Criteria and Definition of Done

The feature works during the demonstration. The button is in the right place. The customer can export a report. There is only one small problem: the agreed security check has not been completed.

Is the work done? A convincing demonstration does not answer that question on its own.

PMP quality questions often turn on the difference between satisfying a specific request and meeting the broader conditions for completed work.

Ask what each condition is checking

Acceptance criteria usually describe conditions a particular item must satisfy. For a report export, examples might include the required columns, file format and access behavior. These details help the people involved agree what the item should do.

In Scrum, the Definition of Done describes the quality state required for an Increment. It creates a shared basis for deciding what counts as completed work. The Scrum Guide states that work which fails this definition is not part of the Increment.

The two concepts can support each other. Meeting an item's functional criteria does not excuse missing a separate quality condition that still applies.

Try this original practice scenario

A Scrum Team completes a report-export feature. Its functional acceptance criteria are satisfied, but a security review required by the team's Definition of Done remains unfinished. A stakeholder asks the team to mark it done so the progress report looks better. What is the best response?

• A. Mark it done because the visible functionality works.
• B. Remove the security review from the definition for this item.
• C. Explain the remaining quality work, keep the status transparent and complete the required review before treating the item as done.
• D. Count half the item as done without discussing the missing review.

C fits the stated conditions. The required review is still outstanding. An attractive progress report does not supply the missing evidence. The team should make the remaining work visible and address it through its normal planning and coordination.

Use the agreement the scenario actually gives you

Do not invent a security review for every question. It matters here because the scenario explicitly says it is required. In another case, the issue might be an unclear acceptance condition, a failed inspection or missing customer authorization.

Identify the unmet condition before choosing the response. If the criteria are ambiguous, clarify them with the appropriate people. If a known defect prevents compliance, address the defect. If the work meets requirements but formal acceptance is pending, follow the applicable acceptance process.

Prevent the argument before the demonstration

Clear examples and shared expectations early in the work reduce last-minute disagreement. Ask how completion will be demonstrated, which checks apply and who needs to participate. That is more useful than discovering at the deadline that three people have four definitions of finished.

When a disagreement occurs, use the agreed conditions and evidence. Avoid blaming the person who identified the gap; finding a problem before release gives the team an opportunity to respond.

Practice reading the missing condition

For each quality scenario, complete this sentence: the work cannot be treated as complete yet because... Then check that your selected action addresses that specific gap.

Register for the free 25-question PMP practice exam for a 30-minute practice session. Review the evidence behind your decisions afterwards and use the results to choose what to study next.