The Sprint Retrospective is a key Scrum event focused on continuous improvement. TheScrum Guidedefines its purpose explicitly as an opportunity for the Scrum Team (Product Owner, Scrum Master, and Developers) to reflect on the past Sprint and identify actionable ways to enhance their effectiveness and quality in the next Sprint. Option C—"Inspect how the last Sprint went and plan improvements for the next Sprint"—accurately captures this intent, aligning with Scrum’s empirical pillars of inspection and adaptation. Let’s evaluate all options:
A (Review stories planned for the next Sprint and provide estimates):This pertains to Sprint Planning or Product Backlog refinement, not the Retrospective. The Retrospective focuses on past performance, not future planning of specific stories or estimation.
B (Demonstrate completed User Stories to the Product Owner):This describes the Sprint Review, where the Increment is showcased to stakeholders, not the Retrospective, which is an internal team event.
C:Correct—the Retrospective is about inspecting the last Sprint (e.g., processes, interactions, tools) and adapting by planning improvements, making it the best answer.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit