What is the maximum length of a Sprint in Scrum?
- A. One week
- B. Two weeks
- C. One month
- D. Three months
Answer: C. One month
Explanation: Sprints are fixed length events of one month or less to create consistency. This ensures regular inspection and adaptation cycles.
Who has the authority to cancel a Sprint?
- A. Scrum Master
- B. Development Team
- C. Product Owner
- D. Stakeholders
Answer: C. Product Owner
Explanation: Only the Product Owner has the authority to cancel the Sprint if the Sprint Goal becomes obsolete.
What event marks the beginning of a new Sprint?
- A. Sprint Review
- B. Sprint Retrospective
- C. Sprint Planning
- D. Daily Scrum
Answer: C. Sprint Planning
Explanation: A new Sprint starts immediately after the conclusion of the previous Sprint, beginning with the Sprint Planning event.
Which of the following activities occur during the Sprint?
- A. Sprint Planning
- B. Daily Scrums
- C. Sprint Review
- D. Sprint Retrospective
Answer: All of the above
Explanation: All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.
Why might shorter Sprints be employed?
- A. To reduce the workload
- B. To generate more learning cycles and limit risk
- C. To increase complexity
- D. To decrease the number of meetings
Answer: B. To generate more learning cycles and limit risk
Explanation: Shorter Sprints can be employed to generate more learning cycles and limit the risk of cost and effort to a smaller time frame.
Which of the following statements are true about changes during the Sprint?
- A. No changes are made that would endanger the Sprint Goal
- B. Quality may decrease if necessary
- C. The Product Backlog is refined as needed
- D. Scope may be clarified and renegotiated with the Product Owner as more is learned
Answers: A, C, D
Explanation: During the Sprint, no changes are made that would endanger the Sprint Goal; quality does not decrease; the Product Backlog is refined as needed; and scope may be clarified and renegotiated with the Product Owner as more is learned.
What are the key benefits of having Sprints in Scrum?
- A. Ensuring inspection and adaptation of progress toward a Product Goal
- B. Allowing for changes in the Sprint Goal as needed
- C. Generating learning cycles
- D. Limiting risk of cost and effort to a smaller time frame
Answers: A, C, D
Explanation: Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month. They generate learning cycles and limit risk of cost and effort to a smaller time frame.
Which practices are useful to forecast progress in a Sprint?
- A. Burn-down charts
- B. Burn-up charts
- C. Cumulative flows
- D. Empiricism
Answers: A, B, C
Explanation: Various practices like burn-downs, burn-ups, and cumulative flows exist to forecast progress. While these are proven useful, they do not replace the importance of empiricism.
When can a Sprint be cancelled?
- A. When the Sprint Goal becomes obsolete
- B. When the Development Team is not performing well
- C. When the Product Owner decides it
- D. When the stakeholders request it
Answers: A, C
Explanation: A Sprint could be cancelled if the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel the Sprint.
What aspects ensure predictability in Scrum through Sprints?
- A. Fixed length events
- B. Regular inspection and adaptation cycles
- C. Allowing changes to Sprint Goal
- D. Empiricism
Answers: A, B, D
Explanation: Predictability is ensured through fixed length events (Sprints), regular inspection and adaptation cycles, and empiricism, which uses past results to make forward-looking decisions. Allowing changes to the Sprint Goal would disrupt predictability.
No comments:
Post a Comment