Answering: “The length of a Sprint should be:” (PSM I)

All three statements describe a good Sprint length: short enough to keep business risk acceptable, short enough to sync with other business events, and no longer than one month. Each one is a valid consideration.

Exam Question

The length of a Sprint should be: (choose the best answer)

• A. Short enough to keep the business risk acceptable to the Product Owner.
• B. Short enough to be able to synchronize the development work with other business events.
• C. No more than one calendar month.
• D. All of the above.

Correct Answer

D. All of the above.

Why This Is the Correct Answer

The Scrum Guide says Sprints are “fixed length events of one month or less to create consistency,” which covers option C. It explains that when a Sprint is too long, the Sprint Goal may become invalid, complexity may rise and risk may increase. That supports option A: the Product Owner, who is accountable for value, needs the risk of each Sprint to stay acceptable. Option B is practical. Aligning Sprint boundaries with business rhythms, such as release windows or reporting cycles, can make feedback and decisions easier. None of these conflicts with the others, so the most complete answer is all of them.

Why the Other Options Are Wrong

A. Short enough to keep business risk acceptable to the Product Owner. Correct on its own, but incomplete. Picking only A ignores the other valid factors.

B. Short enough to synchronize with other business events. Also correct, but not the whole answer.

C. No more than one calendar month. True and stated in the Scrum Guide, yet it is only one of several factors.

Exam Tip

When every option is individually defensible and none contradicts another, “All of the above” is usually the intended answer. Check each one against the Guide first.

Key Takeaways

• Sprints are one month or less.
• Shorter Sprints limit business risk.
• Sprint length can be aligned with business rhythms.