SMC practice question 20 of 25

One week passes by, and less than half of the Product Backlog (requirements) is recorded. The Product Owner believes that it's best to start the first Sprint with this information, rather than waiting for the whole backlog to be completed. What should we do?

Full set: 148 questions

Domain Plan and Estimate Phase

Answer options
A: Yes it's a good time to start the first Sprint Correct answer
B: No, we should wait for the whole backlog to be completed before starting the Sprints
Correct Answer:
A. Yes it's a good time to start the first Sprint
Explanation

The Product Backlog is an emergent and living artifact; it is never considered "complete." Scrum operates on the principle of iterative development, starting with what is known and adapting based on feedback. As long as there are enough well-understood and "Ready" items in the Product Backlog to plan and execute the first Sprint, the team should begin. Waiting for a fully detailed backlog is a waterfall anti-pattern that delays value delivery and feedback.

Why Incorrect

B. This reflects a waterfall mindset. The Product Backlog is intentionally incomplete and evolves throughout the project's lifecycle based on learning and feedback.

References

1. A Guide to the Scrum Body of Knowledge (SBOK® Guide), 3rd Edition. (2017). SCRUMstudy, VMEdu, Inc. Section 3.4, "Product Backlog," p. 68. The guide describes the Product Backlog as an "emergent, ordered list" that is "never complete" and "evolves as the product and the environment in which it will be used evolves."

Scroll to Top