Scrum Events Flashcards
The Sprint Review is just a demo of the Product Backlog items completed during a Sprint. Do you agree?
No, the Sprint Review contains much more activities
No. The Sprint Review contains much more activities to inspect the Increment and adapt the Product Backlog.
For example:
The Product Owner also explains what has not been “Done”;
The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality.
The Scrum Master should not allow the Product Owner to attend the Sprint Planning if the PO is not ready with a Sprint Goal. Is this true or false?
False
The Scrum Team crafts a Sprint Goal during the Sprint Planning.
What are the time-boxes for the Sprint Review and the Sprint Retrospective?
4 and 3 hours respectively
The Sprint Review is at most a four-hour meeting for one-month Sprints.
The Sprint Retrospective is at most a three-hour meeting for one-month Sprints.
Who is the leader in terms of getting feedback from the Key Stakeholders in the Sprint Review?
The Product Owner
The Product Owner is a vital leader in terms of getting feedback from the key stakeholders in the Sprint Review.
Who is responsible for crafting the Sprint Goal at the Sprint Planning?
The Scrum Team
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.
Who has the authority to cancel the Sprint?
The Product Owner
Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.
How long should the Sprint Planning be?
Not more than 8 hours
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
There is no need to decompose all the Items in the Sprint Backlog. It can be done only for the first days of the Sprint.
Select the two meetings in which people outside the Scrum Team are allowed to participate.
- The Sprint Review
- The Sprint Planning
The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice.
The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting
When is the Scrum Team allowed to interact with the Key Stakeholders (select the most applicable option)?
Any time where it’s valuable to have the Stakeholder input
The Product Owner is responsible for making sure that the Key Stakeholders attend and interact in the Sprint Reviews, but really the Stakeholders can be involved with the Scrum Team any time where it’s valuable to have the Stakeholder input.
Who participates in the Sprint Review? Select all applicable variants.
- The Scrum Master
- The Product Owner
- The Key Stakeholders
- The Development Team
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.
In which meetings the Key Stakeholders are allowed to participate?
The Sprint Review
The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time.
What provides guidance to the Development Team on why it is building the Increment?
The Sprint Goal
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.
Who participates in the Sprint Planning? Select three.
- The Product Owner
- The Development Team
- The Scrum Master
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
What happens during the Sprint? Select three answers.
- No changes are made that would endanger the Sprint Goal
- Quality goals do not decrease
- Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned
During the Sprint:
- No changes are made that would endanger the Sprint Goal;
- Quality goals do not decrease; and,
- Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
The Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
True
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
