TheSprint Retrospectiveis a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This event focuses oncontinuous improvementby reviewing processes, collaboration, tools, and their adherence to the Definition of Done.
According to the2020 Scrum Guide, the Sprint Retrospective serves the following purposes:
* Toinspecthow the last Sprint went in terms of individuals, interactions, processes, tools, and the Definition of Done.
* To identify andagree upon actionable improvementsthat will increase the team's effectiveness in future Sprints.
Why the other options are incorrect:
* B. Plan the incomplete work for the next Sprint and submit reasons to the Product Owner:This is not the purpose of the Sprint Retrospective. Sprint Planning is the event where the team plans the upcoming Sprint.
* C. Explain what Backlog items have been done and what has not been done:This describes the Sprint Review, where the team discusses completed and incomplete Product Backlog Items with stakeholders.
* D. Identify Developers who did not perform well in the Sprint:Scrum encourages collaboration, respect, and continuous improvement, not blaming individuals for shortcomings.