The Post-Project Phase

This is one of the six phases in the DSDM^® Process, which can be configured in different ways to create various types of lifecycle for the project.

graph TD rp(Pre-Project) --> fs(Feasibility) fs --> fn(Foundations) fn --> ed(Evolutionary Development) ed --> dp(Deployment) dp --> ed dp --> fn dp -.-> fs dp --> sp(Post-Project) style sp fill:#000,stroke:#000,color:#fff

The post-project phase is run when everything else is finished in the project, and we’re ready to close it. Based on DSDM’s philosophy, which requires its special approach to project variables with a fixed duration, and its principle of deliver on time, the project as a whole is timeboxed and must be finished on time. As a result, the post-project phase always has a predetermined time.

The usual closing concept present in other systems, such as PRINCE2^®'s closing a project process and the PMBOK^® Guide’s closing process group, contain several activities, including those for tying up loose ends. DSDM’s post-project phase, on the other hand, is about a subset of the usual closing activities: Checking to see how well the expected benefits are realized. This is so, because other activities (e.g., tying up loose ends) are done continuously during a DSDM project.

The pre-project and post-project phases are about a certain type of activities that mainly belong to the program and portfolio management layers. The reason they are mentioned in DSDM, which is a project management method, is to support those higher layers.

Written by Nader K. Rad

This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.

This wiki is developed and managed by an accredited trainer, independent of Agile Business Consortium and APMG. While aligned with their guidelines, it’s not an official resource.