CAPM Practice: Determine how to plan project iterations

User stories should be appropriately sized — split into smaller, more granular stories if needed — so they can be completed within a single iteration. This ensures incremental delivery and reduces risk.

**Why not A:** Making stories as large as possible increases risk, delays feedback, and makes estimation less accurate. Large stories are harder to complete within a single iteration and reduce the team's ability to deliver predictable increments. The overhead of smaller stories is minimal compared to the benefits.

**Why not C:** Requiring uniform story size ignores the natural variation in complexity across different features. Stories should be appropriately sized (small enough to fit in an iteration) but not artificially forced to identical sizes, which would distort estimation and reduce planning flexibility.

**Why not D:** Sizing based on team member seniority would mean the same story gets different estimates depending on who is assigned to it. Agile estimation uses relative sizing (story points) based on complexity and effort, independent of which individual will implement it, because the team collectively owns delivery.