What is achieved in the Sprint Retrospective?
The Scrum Team is a self-organized team that continuously improves its way of working Sprint to Sprint without any external push. Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspecting the Scrum Team itself.
-------------------Question- 41--------------------------
What is inspected in the Sprint Retrospective and potentially adapted in the next Sprint?
a) Sprint Improvement Plan
b) Scrum Team
c) Sprint Backlog
-------Answer-------
Correct answer is ‘b.’
-------------------Question- 41--------------------------
Who leads and controls the Sprint Retrospective?
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvement to be enacted during the next Sprint.
The Scrum Master participates as a peer team member in the meeting from the accountability of the Scrum process. The Scrum Master or any individual does not lead or control the event. The Scrum Master ensures that the event takes place and that attendants understand its purpose and teaches all to keep it within the time-box. This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
What happens in the Sprint Retrospective?
The Scrum Team inspects how the last Sprint went with regards to people, relationships, processes, and tools. It identifies and orders the major items that went well and potential improvements. It also creates a plan for implementing improvements to the way the Scrum Team does its work.
The Scrum Master encourages the Scrum Team to improve its development processes and practices to make it more effective and enjoyable for the next Sprint. The changes, however, must still occur within the Scrum process framework.
Does the Retrospective also review the product or work outcome?
No, the Product Increment is already reviewed by the Scrum Team and stakeholders in the Sprint Review. The Retrospective is about improving the way the product is built. It is not only the improvements of how Scrum is implemented by the team, but also the engineering practices like coding, testing, integration, deployment, etc.
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of “Done” as appropriate.
Outcome
By the end of the Sprint Retrospective, the Scrum Team should have identified improvements to implement in the next Sprint. Implementing these improvements is the adaptation to the inspection of the Scrum Team itself. To ensure discipline in implementation, at least one high priority improvement is identified to be added to the Sprint Backlog of the next Sprint.
Can a Scrum Team change fundamentals of Scrum in the name of improvement?
The Scrum Team can make improvement plans on development processes and practices, but it cannot change the fundamentals of the Scrum framework itself.
-------------------Question- 42--------------------------
Which is true?
a) The Retrospective focuses on the Scrum Team's processes and people, and the Sprint Review focuses on the product.
b) The Retrospective focuses on the product, and the Sprint Review focuses on the Scrum Team's processes.
c) The Retrospective focuses on the Scrum Team's processes and people, and the Sprint Review focuses on velocity.
-------Answer-------
Correct answer is ‘a.’
-------------------Question- 42--------------------------
Summary
• The Sprint Retrospective is a formal opportunity where the Scrum Team inspects itself and creates a plan for improvement for the next Sprint. At least one high priority improvement is identified to be added to the Sprint Backlog of the next Sprint.
• This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
• The Scrum Master encourages the Scrum Team to improve its development processes and practices.
• The Scrum Team plans ways to increase product quality by adapting the definition of “Done.”
• The outcome is a list of identified improvements to be implemented in the next Sprint.