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

Predictive project closeout involves: obtaining formal acceptance of deliverables; completing final documentation (lessons learned, final report, project archive); releasing team members and resources back to the organization; closing contracts; and ensuring all administrative matters are complete. These activities formally end the project and transfer knowledge to the organization.

**Why not A:** Starting work on the next project in the portfolio is a portfolio management activity, not a project closeout activity. Formal closeout focuses on completing and archiving the current project, not initiating new ones.

**Why not B:** Transitioning the team to an agile approach for future work is a methodology decision unrelated to project closeout. Closeout activities address the current project's completion, not the methodology for future projects.

**Why not D:** Creating a new WBS for a post-implementation phase would be part of a separate project's planning, not part of the current project's closeout. Formal closeout ends the project; it does not begin planning for what comes next.