Inspection
Inspection is the regular examination used within empirical process control to confirm that the project's deliverables conform to stated requirements.
Key Points
- Supports empirical process control by frequently examining work and outcomes.
- Checks deliverables against requirements, acceptance criteria, and the Definition of Done.
- Findings should trigger adaptation when variances are discovered.
- Common techniques include peer reviews, walkthroughs, testing, and checklists during events like reviews and demos.
Example
During a sprint, a Scrum team performs a code review and demo of a new feature. Using a checklist based on acceptance criteria and the Definition of Done, they notice the API lacks the required error handling. The team logs a task, fixes the gap, and re-tests before the sprint review, where stakeholders verify the increment meets the stated requirements.
PMP Example Question
In an agile project using empirical process control, the team wants to ensure the increment meets agreed requirements before release. Which action best represents inspection?
- Hold a sprint review with stakeholders to evaluate the increment against acceptance criteria and the Definition of Done.
- Change the workflow to remove a bottleneck identified last iteration.
- Reprioritize the product backlog based on new market insights.
- Add schedule buffer to account for potential defects.
Correct Answer: A — Conduct a review to examine the increment against explicit criteria
Explanation: Inspection is about examining work results against requirements. Option A directly checks the increment against acceptance criteria and the Definition of Done; the others describe adaptation or planning activities.
