In Agile software development, what is the primary purpose of a 'sprint retrospective' meeting, as distinct from a 'sprint review'?

The sprint retrospective is an internal, team-only meeting held at the end of a sprint specifically to reflect on how the team worked together during that sprint — what went well, what didn't, and what specific process improvements to try in the next sprint. This is distinct from the sprint review (option A), which is an outward-facing meeting demonstrating the completed, working software to stakeholders and gathering their feedback on the product itself, rather than the team's internal process. Backlog estimation (option B) typically happens during backlog refinement or sprint planning, budget sign-off (option D) is not a standard Agile ceremony, and task assignment (option E) is generally part of sprint planning, not the retrospective.