Closing the Project
To most of us, it may be common sense that every start has a finish. A project that has been started will have some kind of ending. As I explained in Chapter 1, people have been doing projects since before there was a field of project management. The unde
- PDF / 281,246 Bytes
- 12 Pages / 439.37 x 666.142 pts Page_size
- 82 Downloads / 217 Views
15 Closing the Project PMP Exam Objectives
What It Really Means
5.1 Obtain final acceptance of the project deliverables
Obtain final acceptance of the project deliverables from relevant stakeholders in order to confirm that project scope and deliverables were achieved.
5.2 Transfer ownership of deliverables
Transfer ownership of deliverables to the assigned stakeholders in accordance with the project plan in order to facilitate project closure.
5.3 Obtain financial, legal, and administrative closure
Obtain financial, legal, and administrative closure using generally accepted practices and policies in order to communicate formal project closure and ensure transfer of liability.
5.4 Prepare and share the final project report
Prepare and share the final project report according to the communications management plan in order to document and convey project performance and assist in project evaluation.
5.5 Collate lessons learned
Collate lessons learned that were documented throughout the project and conduct a comprehensive project review in order to update the organization’s knowledge base.
5.6 Archive project Archive project documents and materials using generally documents and materials accepted practices in order to comply with statutory requirements and for potential use in future projects and audits. 5.7 Obtain feedback from relevant stakeholders
Obtain feedback from relevant stakeholders using appropriate tools and techniques and based on the stakeholder management plan in order to evaluate their satisfaction.
© Paul Sanghera 2019 P. Sanghera, PMP® in Depth, https://doi.org/10.1007/978-1-4842-3910-0_15
538
Chapter 15 | Closing the Project To most of us, it may be common sense that every start has a finish. A project that has been started will have some kind of ending.As I explained in Chapter 1, people have been doing projects since before there was a field of project management.The underlying philosophy of project management is to perform projects deliberately—that is, to plan them, to monitor and control them, and so forth. Finishing a project deliberately means finishing it in a controlled way, not just letting it finish—even when it’s cancelled. That’s right. Whether completed or cancelled, a project needs to be properly closed. The closing efforts are coordinated by the integration management process called Close Project or Phase. As you will see in this chapter, during its closure, the project meets itself from start to end in the self-assurance and review mode to ensure that everything planned has been done and been done according to the plan, as well as for a general review of the whole project. So, the core issue in this chapter is how to properly close a project. In search of an answer, we will explore three avenues: the big picture of the project closure in the context of the whole project, core project closure, and project review and lessons learned.
Closing the Project: Big Picture As mentioned earlier, the closing efforts are coordinated by an integration management process ca
Data Loading...
