Question 33 - Which is the true statement?
-
The Sprint Retrospective focuses on the product while the Sprint Review focuses on Scrum Team’s process and people aspects
-
The Sprint Retrospective focuses on Scrum Team’s process and people aspects while the Sprint Review focuses on velocity
-
The Sprint Retrospective focuses on Scrum Team’s process and people aspects while the Sprint Review focuses on the product
Overall explanation
-
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
-
The purpose of the Sprint Retrospective is to:
• Inspect how the last Sprint went with regards to people, relationships, process, and tools;
• Identify and order the major items that went well and potential improvements; and,
• Create a plan for implementing improvements to the way the Scrum Team does its work.
Question 46 - Which of the following might the Scrum Team discuss during a Sprint Retrospective?
-
Methods of communication
-
Skills needed to improve the Development Team's ability to deliver
-
The way the Scrum Master participates in the Sprint Planning
-
All of the above
-
Its Definition of "done"
Overall explanation
-
The purpose of the Sprint Retrospective is to:
-
Inspect how the last Sprint went with regards to people, relationships, process, and tools;
-
Identify and order the major items that went well and potential improvements; and,
-
Create a plan for implementing improvements to the way the Scrum Team does its work.
-
-
The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint.
-
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with product or organizational standards.
-
By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself.
-
Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
Question 88 - Which topics are NOT appropriate in a Sprint Retrospective?
Choose 2 answers
-
The value of work currently represented in the Product Backlog
-
Definition of "Done"
-
Sprint Backlog for the next Sprint
-
Team relations
Overall explanation
- The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
- The purpose of the Sprint Retrospective is to:
Inspect how the last Sprint went with regards to people, relationships, process, and tools;
Identify and order the major items that went well and potential improvements; and,
Create a plan for implementing improvements to the way the Scrum Team does its work.
Question 115 - A Scrum Master is introducing Scrum to a new Development Team. The Development Team has decided that a retrospective is unnecessary. What action should the Scrum Master take?
-
Comply with the decision of the self-organizing team
-
Call a meeting between the Development Team and senior management
-
Begin facilitating productive and useful retrospectives
-
Consult with the Product Owner to see how he/she feels about the situation
Overall explanation
- The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
- The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose.