CAPM Practice: Determine how to plan project iterations

Scrum recommends Sprints of one to four weeks. The length should remain consistent to establish a predictable cadence. Variable length undermines velocity tracking and team rhythm.

**Why not A:** While two-week sprints are common, the Scrum Guide does not mandate exactly two weeks. Sprints can range from one to four weeks depending on team context, product complexity, and stakeholder feedback needs. Prescribing an exact duration contradicts Scrum's empirical approach.

**Why not B:** Three months far exceeds Scrum's recommended sprint length. Longer cycles delay feedback, increase risk of building the wrong thing, and prevent the frequent inspection and adaptation that is central to Scrum's effectiveness.

**Why not D:** Variable sprint durations undermine the team's ability to establish a reliable velocity, forecast future work, and maintain a sustainable cadence. Consistent sprint length is fundamental to Scrum's empirical process control framework.