Why should the Product Owner be present at the Daily Scrum?
Correct Answer:
A
The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event for the Development Team, and the Product Owner can attend only if invited by the Development Team.
What two factors are best considered when establishing the Sprint length? (Choose two.)
Correct Answer:
BD
The correct answers are B and D, because the length of the Sprint should be chosen based on the level of uncertainty over the technology to be used and the risk of being disconnected from the stakeholders. The Scrum Guide states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase.”
What is the best suited structure for Development Teams in order to produce integrated Increments?
Correct Answer:
B
According to the Scrum Guide1, an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, an Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, in order to produce integrated Increments that are potentially releasable, the best suited structure for Development Teams is to develop functionality from beginning to end throughout all technical layers.
References: Scrum Guide
What is the recommended size for a Scrum Team? (Choose the best answer.)
Correct Answer:
C
The recommended size for a Scrum Team is 10 or fewer people, as stated in the Scrum Guide: “The recommended size of a Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”
A new developer is having continuing conflicts with existing Development Team members and creating the hostile environment. If necessary, who is responsible for removing the team member?
Correct Answer:
C
The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product
Backlog into Increments of potentially releasable functionality.” Therefore, the Development Team should
manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.
