What is the primary purpose of retrospectives in an engineering project?

• A. To assign blame for failures.
• B. To review what worked, what didn’t, and plan improvements for future iterations.
• C. To publish performance metrics.
• D. To finalize requirements with no changes.

Answer: (B)

Retrospectives are a learning check-in after each cycle where the team looks back to see what worked well, what didn’t, and what changes should be made to improve next time. The goal is to improve the process, collaboration, and overall delivery, not to assign blame or lock in fixed requirements. By identifying concrete, actionable improvements and assigning owners, the team continually enhances quality and speed in future iterations.