Sprint Planning Flashcards
How many Sprints are planned during the Sprint Planning event?
At least 1
Exactly one
Exactly 2
As many as possible as long as the time box does not expire
Exactly one
The purpose of the Sprint Planning is to plan a single Sprint.
Who must attend the spring planning meeting
The Scrum team
In the first two parts the entire scrum team. For the last part only the developers are needed
The scrum team, the developers and other experts
The developers and the product owner
The scrum team
What is the time-box for the Sprint Planning meeting if the Sprint is two-weeks?
8 hrs
4 hrs
3 hrs
It depends on the complexity of the PBIs
8 hrs
I know this is confusing, but regardless of the length of the Sprint, the time-box is still 8 hours. The event is usually shorter for shorter Sprints, but the Scrum Guide does not specify it should be proportionally shorter. In practice, the rule of thumb is to make it proportionally shorter.
The Stakeholders are allowed to participate in the Sprint Planning meeting to clarify the Product Backlog Items and provide advice.
True
False
False
The Scrum Team may invite external people to attend the meeting and provide technical or domain advice – this is not the same as saying they invite Stakeholders. Nobody attends without being invited. The Stakeholders are mentioned in the Scrum Guide as participating in the Sprint Review meeting. They have nothing to do with the Sprint Planning meeting. If Stakeholders attend this meeting, they attend as domain experts (or similar) and provide advice.
Complete the following sentence:
The Sprint Goal belongs to _____
Developers Stakeholders The entire scrum team The product owner The scrum master
The entire scrum team
The Sprint Goal is shared by the entire Scrum Team, not just the Developers.
What do the selected Product Backlog Items during the Sprint Planning represent?
A forecast
A commitment
A goal
A plan
The selected items are a forecast for what will be accomplished in the Sprint. It is not a commitment or a promise. The Scrum Guide v2020 explains: “Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.”
During the Sprint Planning meeting, each Sprint Backlog Item is assigned to a single Develop
True
False
In Scrum, work is never assigned. All Developers take ownership over the Sprint Backlog and the Sprint Backlog Items, never individual Developers.