Q151. Who should make sure everyone on the Scrum Team does his or her tasks for the Sprint?
A. The Project Manager.
B. The Product Owner.
C. The Scrum Master.
D. The Scrum Team.
E. All of the above.
Answer
D
Q152. When is it most appropriate for a Development Team to change the definition of `Done`?
A. During Spring Planning.
B. Prior to starting a new Sprint.
C. During the Sprint Retrospective.
D. Prior to starting a new project.
Answer
C
Q153. The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)
A. Opportunities to inspect and adapt the Sprint Backlog are lost.
B. Impediments are raised and resolved more slowly.
C. The Product Owner cannot accurately report progress to the stakeholders.
D. Too much work is spent updating the Scrum board before the meeting.
E. The Scrum Master loses the ability to update the Gantt chart properly.
F. The Sprint plan may become inaccurate.
Answer
A, B, F
Q154. Which statement best describes Scrum?
A. A defined and predictive process that conforms to the principles of Scientific Management.
B. A complete methodology that defines how to develop software.
C. A cookbook that defines best practices for software development.
D. A framework within which complex products in complex environments are developed.
Answer
D
Q155. Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)
A. Economic Value Added.
B. Respect.
C. Focus.
D. Earned Value.
E. Courage.
Answer
B, C, E
Q156. When many Scrum Teams are working on the same product, should all of their Increments be integrated into every Sprint?
A. Yes, but only for Scrum Teams whose work has dependencies.
B. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
C. No, each Scrum Team stands alone.
D. No, that is far too hard and must be done in a hardening Sprint.
Answer
B
Q157. When can a Development Team cancel a Sprint?
A. It can’t. Only Product Owners can cancel Sprints.
B. When functional expectations are not well understood.
C. When the Product Owner is absent too often.
D. When the selected Product Backlog items for the Sprint become unachievable.
E. When a technical dependency cannot be resolved.
Answer
A
Q158. Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?
A. The Sprint Backlog.
B. The Sprint Goal
C. The release plan.
D. Sprint Review minutes.
Answer
B
Q159. How should a Development Team deal with non-functional requirements?
A. Ensure every Increment meets them.
B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
C. Handle them during the Integration Sprint preceding the Release Sprint.
D. Assign them to the lead developers on the team.
Answer
A
Q160. When is Sprint over?
A. When the Product Owner says it is done.
B. When all Product Backlog items meet their definition of `Done`.
C. When all the tasks are completed.
D. When the time-box expires.
Answer
D