Scribd
Upload
73 views19 pages

Unit Objectives Manage Project Closure

The document discusses several key activities involved in closing out a project: conducting a customer acceptance meeting to obtain sign-off, turning over final deliverables, closing out vendor contracts, releasing project team members, performing a project review to identify lessons learned, compiling a project report documenting the project history and outcomes, and ensuring all closure activities address the needs of stakeholders.

Uploaded by

Donatas Sedys
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
73 views19 pages

Unit Objectives Manage Project Closure

The document discusses several key activities involved in closing out a project: conducting a customer acceptance meeting to obtain sign-off, turning over final deliverables, closing out vendor contracts, releasing project team members, performing a project review to identify lessons learned, compiling a project report documenting the project history and outcomes, and ensuring all closure activities address the needs of stakeholders.

Uploaded by

Donatas Sedys
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 19

Project closure

Unit objectives
 Manage project closure
TLI esr uo C
Topic A
Topic A: Closing a project
TLI esr uo C
Closure activities
 Addresses the needs of all
stakeholders involved in the project
 Many stakeholders needs are different
at the end of the project than at project
inception
TLI esr uo C

 After a project
– Recognize work done and provide a
sense of completion
– Review lessons learned

continued
Project activities
 Closure activities
– Meet with customers to gain final
approval of the deliverable
– Hand over the project deliverable and
begin support/maintenance
– Close out vendor contracts
TLI esr uo C

– Perform a project review


– Compile a project report
– Complete the project billing
– Return project resources
– Collect project files and store them for
future access
Customer acceptance meeting
 Verify the acceptance criteria for the
project have been met
 Obtain customer sign-off
 Dealing with a dissatisfied customer
requires an agreement, in writing, on
next steps such as:
TLI esr uo C

– Project acceptance with deviations and


omissions noted and explained
– Project acceptance with monetary or other
compensation to the customer or project
sponsor for the deviations and omissions
– Continuation of project until all
acceptance/success criteria are achieved
Turning over the deliverable(s)
 After customer sign-off, turn over the
deliverable to the client
 Begin support/maintenance
TLI esr uo C
Closing out vendor contracts
 Contract conditions have been met
 Work specified has been completed
 Deliverables have been tested and
accepted
 The vendor has been notified that:
TLI esr uo C

– The deliverables have been accepted


– The contract is complete
Releasing the project team
 Release team members at the end of
the project
 Notify functional managers
TLI esr uo C
TLI esr uo C Activity A-1

Discussing the closure phase


Conduct a project review
 Include all aspects of the project
 Identify which aspects were
successful and which need
improvement
 Identify possible improvements to
TLI esr uo C

existing processes
 Conduct the review near the end of
the project
 Include all team members
Objectives of project reviews
 Learn from experience
 Repeat successes
 Handle less successful events
differently
 Provide data for others
TLI esr uo C

 Identify faulty processes


Suggested considerations
 Project definition, scope and team
 Planning
 Cost
 Resources
 Communications
TLI esr uo C

 Reflection
Reflective questions
 What did you enjoy most and why?
 What did you find frustrating and why?
 What was successful?
 What didn’t work?
 What wasn’t achieved
TLI esr uo C

 If you participate on another team, what


one thing would you make sure was in
place?
 In hindsight, what would you have done
differently?
TLI esr uo C Activity A-2

Conducting a project review meeting


Identify lessons learned
 Gather throughout life of project
 Review at end of each major phase
 Identify and analyze in detail
 Dynamic, not static
 Self-contained
TLI esr uo C

 About processes and people


Compile a project report
 A final report is:
– History of project
– Synopsis of what went right and wrong
– Account of the life and times of the
project
– Account of who worked on the project
TLI esr uo C

and in what capacity


– Account of how the project was managed

continued
Compile a project report
 Project report includes:
– A brief description of project
– A measure of success
– Lessons learned
– Explanations for any variances in time or
budget
TLI esr uo C

– Recommendations for future projects


TLI esr uo C Activity A-3

Discussing the project report and lessons


learned
Unit summary
 Discussed project closure, learned
about customer acceptance meetings,
project reviews and creating a project
report
TLI esr uo C

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy