Please select the option(s) that NOT adhere to the purpose of this important Scrum meeting:
[A] Discuss the impediments raised by the Development Team during the last sprint, and make a plan for implementing improvements.
[B] Refinement of epics nominated by the Product Owner for the next couple of sprints, in order to promote reliable release planning.
[C] Verification of how well the product increment satisfies the applicable user stories in the Product Backlog.
[D] Discuss the interaction within the Scrum Team, and agree upon measures to improve the collaboration.
[B] Refinement of epics nominated by the Product Owner for the next couple of sprints, in order to promote reliable release planning. [C] Verification of how well the product increment satisfies the applicable user stories in the Product Backlog. --> The Sprint Retrospective is an opportunity forRead more
[B] Refinement of epics nominated by the Product Owner for the next couple of sprints, in order to promote reliable release planning.
[C] Verification of how well the product increment satisfies the applicable user stories in the Product Backlog.
–>
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for identified and agreed-upon improvements to be enacted during the next Sprint(s).
Thus, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
Refinement of epics is part of the regular grooming exercise under auspicien of the Product Owner, and is not part of the retrospective.
Only during Sprint Review, it is determined whether the product increment satisfies the applicable items on the Product Backlog according to the ‘Definition of Done’.
See less