CAPM Practice: Demonstrate an understanding of common problem-solving tools and techniques

Retrospectives (used especially in agile contexts) are structured team meetings for reflection and improvement. The team reviews the process (not just the product), identifies what worked well and what didn't, and agrees on specific improvements to implement going forward.

**Why not A:** Obtaining formal acceptance of completed deliverables is the purpose of a sprint review or acceptance meeting, not a retrospective. Retrospectives focus on process improvement — what worked, what didn't, and how to improve — rather than product acceptance.

**Why not B:** Assigning tasks for the next iteration happens during sprint planning, not during a retrospective. The retrospective looks backward at the process to identify improvements, while sprint planning looks forward to determine what work will be done next.

**Why not D:** Reporting project status to stakeholders is done through status reports or sprint reviews, not retrospectives. Retrospectives are internal team meetings focused on process reflection and improvement, not external stakeholder communication.