In Scrum, Sprints are continuous and fixed-length, with no gaps allowed between them. TheScrum Guide explicitly states: "A new Sprint starts immediately after the conclusion of the previous Sprint." This ensures a consistent cadence of delivery and adaptation, a cornerstone of Scrum's empirical process. Let's examine each option:
* A (Not enough "Ready" items):The Product Backlog can be refined incrementally; a lack of "Ready" items doesn't justify delaying a Sprint. The team can start with what's available and refine further during the Sprint.
* B (No Sprint Goal):The Sprint Goal is defined during Sprint Planning, not beforehand. Its absence pre- Sprint isn't a valid delay reason.
* C:This aligns with theScrum Guide's mandate for immediate succession, making it correct.
* D (QA needs more time):Scrum rejects external dependencies like a separate QAdepartment; the Developers must deliver a "Done" Increment within the Sprint. Delaying contradicts this.