6 Quality Planning and Delivery Online Quiz Questions

True

False

The objective is the requirement; the acceptance criterion is the measurement method and owner.

The objective describes the quality outcome; the acceptance criterion states the condition or evidence needed for acceptance.

The objective is written after delivery; the acceptance criterion is decided by the project team alone.

The objective describes who approves the work; the acceptance criterion describes the project schedule.

Verification checks user satisfaction; validation checks whether scheduled reviews occurred.

Verification checks whether the process was followed; validation checks whether the deliverable meets a specification.

Verification checks conformity to specified requirements; validation checks whether the deliverable meets users’ needs in context.

Verification and validation are two names for inspecting a deliverable against its acceptance criteria.

True

False

Standards, procedures, roles, and approval authority

A guarantee that no defects will occur

Quality metrics and planned review or test activities

Required records and how nonconforming work and changes will be handled

A rule that every project must use the same level of quality-plan detail

Treat the improvement as successful as soon as it is implemented.

Measure whether the change produced the intended result.

Stop collecting quality data so staff will not be distracted by metrics.

Replace the existing acceptance criteria with whatever results the change produces.

Record the issue, the affected criterion, its severity, and relevant evidence.

Quietly lower the acceptance standard so the item can pass.

Prevent the item from being used or released until its status is clear.

Close the issue immediately after correction without rechecking the work.

Correct or rework the item through an authorized process.

True

False

Use the same sampling rate for every deliverable so results are comparable.

Reduce checks whenever a project has a tight schedule, regardless of risk.

Use more rigorous or frequent checks where failure would have greater consequences.

Rely only on final inspection for high-risk work because it catches defects after completion.

The form should be attractive and modern.

A valid submission is stored with all required fields, and invalid email formats are rejected with a clear message.

The team should make the form convenient for everyone.

The form should use the project’s preferred design style.

Quality assurance, because the team is checking whether a planned process is followed.

Quality control, because every scheduled review is an inspection of the finished product.

Validation, because following a review schedule proves the product meets users’ needs.

Acceptance, because a review schedule is itself a customer approval.

Verification, because any test with users checks only technical conformance.

Quality assurance, because a pilot examines whether project procedures were followed.

Validation, because the pilot checks whether the guide works for users in its intended context.

Quality control only, because user needs cannot be evaluated through a pilot.

Mark the item accepted so downstream work can continue without delay.

Seek a formally approved change or concession from the authorized decision-maker.

Revise the acceptance criterion informally and omit the original result from the record.

Stop recording the defect once the team has agreed that it is inconvenient to fix.