CAPM Practice: Determine how to document project controls of predictive, plan-based projects

In a predictive project, phase boundaries are marked by formal phase reviews (stage gates). Management reviews the phase deliverables, verifies they meet defined criteria, and formally decides: Go (approve and fund the next phase), No-Go (terminate the project), or Hold (pause for additional analysis). This is the governance checkpoint that marks the formal end of one phase and authorization of the next.

**Why not A:** While a retrospective can be valuable for capturing lessons learned, it is an informal team activity that does not constitute formal phase closure. Predictive projects require management-level review and formal authorization to proceed, which a retrospective does not provide.

**Why not B:** Beginning work on the next phase before formal approval violates predictive project governance. Phase transitions require explicit management authorization through a stage-gate review. Starting next-phase activities without this approval bypasses the governance checkpoint.

**Why not D:** Updating the project schedule is a routine project management activity, not a formal phase closure marker. While the schedule should reflect phase completion, the update itself does not constitute the formal review and authorization that marks a phase boundary.