18 Questions
What is the purpose of a Sprint Retrospective in Scrum?
To evaluate the last Sprint's approach and identify improvements
When does the Sprint Retrospective take place in the Scrum framework?
Second to last event of the Sprint
What is a key aspect of the Sprint Review meeting?
Collaboration between the Scrum Team and stakeholders
During a Sprint Review, what is discussed to acknowledge both successes and failures?
Acknowledge what went well and what didn’t
What is the timing for a Sprint Review in a one-month Sprint?
Timeboxed to a maximum of three hours
Which Scrum event represents work or value and ensures transparency for key information?
Sprint Review
What is the main focus of the Daily Scrum meeting?
Inspecting progress towards Sprint Goal and planning next day's work
Who are the primary participants in the Daily Scrum meeting?
Developers, with the Product Owner and Scrum Master if they are actively working on Sprint Backlog items
What is the maximum duration of a Daily Scrum meeting in a one-month Sprint?
15 minutes
What is the primary purpose of the Sprint Review?
Reviewing the Increment and gathering feedback from stakeholders
When is a Sprint Retrospective typically held?
At the end of the Sprint
Who is responsible for facilitating the Sprint Retrospective?
Scrum Master
What is the primary purpose of the Sprint Retrospective event in Scrum?
To inspect how the last Sprint went with regards to people, relationships, process, and tools
Which of the following is NOT a typical member of the Scrum Team?
Project Manager
What is the primary purpose of the Sprint Review event in Scrum?
To inspect the Increment and adapt the Product Backlog if needed
Which of the following is NOT typically discussed during Sprint Planning?
The Daily Scrum schedule
What is the primary purpose of the Daily Scrum event in Scrum?
To identify and remove impediments to the Development Team's progress
Which of the following is a key topic addressed during Sprint Planning?
Sprint Goal
Study Notes
Scrum Events
- Scrum Team showcases work to stakeholders, discussing progress toward the Product Goal, and collaborates on next steps.
- The event is encouraged as a working session, not just a presentation, and is timeboxed to a maximum of four hours for a one-month Sprint.
Sprint Review
- The purpose is to plan for increasing quality and effectiveness, inspecting the last Sprint's approach to individuals, processes, tools, and the Definition of Done.
- The team identifies and explores misleading assumptions, acknowledges what went well and what didn’t, and addresses problem-solving effectiveness.
- The event aims to improve team effectiveness, prioritize impactful improvements, and determine most helpful changes.
Sprint Retrospective
- The purpose is to represent work or value, ensure transparency for key information, and plan for increasing quality and effectiveness.
- The event is timeboxed to a maximum of three hours for a one-month Sprint and identifies opportunities for improvement.
- The team determines the most helpful changes for team effectiveness and prioritizes impactful improvements for immediate action or the next Sprint Backlog.
Sprint Capability
- Developers select Product Backlog items for the Sprint, refining them for better understanding and confidence.
- Selection is based on past performance, upcoming capacity, and the Definition of Done.
Execution Planning
- Developers plan the work necessary to create an Increment that meets the Definition of Done for each selected Product Backlog item.
- Product Backlog items may be broken down into smaller work items of one day or less.
- The outcome is the Sprint Goal, selected Product Backlog items, and the delivery plan forming the Sprint Backlog.
Daily Scrum
- The purpose is to inspect progress towards the Sprint Goal and adapt the Sprint Backlog accordingly.
- The event is timeboxed to 15 minutes, occurring at the same time and place every working day of the Sprint.
- Participants include Developers, with the Product Owner and Scrum Master as Developers if they are actively working on Sprint Backlog items.
Sprints
- Sprints are the heartbeat of Scrum, where ideas are turned into value.
- They are fixed-length events of one month or less, creating consistency, and a new Sprint starts immediately after the conclusion of the previous Sprint.
- A Sprint could be canceled if the Sprint Goal becomes obsolete, but only the Product Owner has the authority to cancel the Sprint.
Learn about the Scrum Sprint Review meeting, where the team showcases work to stakeholders, discusses progress towards the Product Goal, collaborates on Sprint achievements and plans for the next steps. Understand the approach and timing of this important event in the Scrum framework.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
