CAPM Practice: Determine how to plan project iterations

Stories that are too large for a single sprint are called 'epics' and must be split into smaller, independently deliverable stories. Story splitting techniques include splitting by workflow steps, business rules, data variations, or acceptance criteria. Well-sized stories (completable in one sprint) enable accurate velocity measurement, regular feedback, and consistent Done increment delivery.

**Why not A:** Permanently removing a story just because it is too large wastes potentially valuable functionality. The story likely represents real user needs — the solution is to break it into smaller deliverable pieces, not to discard it entirely.

**Why not B:** Committing to an oversized story and planning overtime is unsustainable and undermines the team's ability to maintain a consistent velocity. Scrum values sustainable pace, and committing to work the team cannot realistically complete sets the sprint up for failure.

**Why not C:** Deferring the story indefinitely because the team "isn't fast enough" ignores the actual solution: story splitting. The issue is not team speed but story size. Any story can be decomposed into smaller, independently valuable pieces that fit within a sprint.