CAPM Practice: Determine how to plan project iterations

Hybrid projects require explicit coordination between iterative and sequential components. Iteration plans should identify touchpoints, dependencies, and handoffs between the two approaches to prevent bottlenecks and integration issues.

**Why not B:** Eliminating sequential components entirely ignores the legitimate reasons certain work must be done in a fixed order—regulatory approvals, hardware procurement, infrastructure builds, and other activities with hard dependencies cannot always be made iterative. Forcing all work into iterations can create artificial complexity and risk for work that is well-understood and benefits from a predictive approach.

**Why not C:** Keeping the two approaches completely separate defeats the purpose of hybrid project management. Agile and predictive components in the same project share resources, timelines, and deliverables; failing to integrate their planning creates gaps, missed handoffs, and schedule conflicts that can derail both tracks.

**Why not D:** Converting sequential work to agile sprints immediately is an overreaction that ignores the fundamental characteristics making certain work better suited to a predictive approach. Sequential work often exists because of regulatory, contractual, or technical constraints—wrapping it in sprint ceremonies does not make it inherently adaptive and can create process overhead without any corresponding benefit.