Please enable JavaScript.
Coggle requires JavaScript to display documents.
Lecture 17 - Project Closure (Project Manager Role in Closure? (Conduct…
Lecture 17 - Project Closure
Involving gaining stakeholders and customers acceptance of the final project
Even if not completed, should be formally closed in order to reflect what can be learnt for future projects
Formal termination of all activities in project
Outputs
Project archives and lessons learnt - Part of organizational assets
Also include final report and presentation to sponsor or senior management
Types
Termination by integration/by addition
Used as input for another project
Termination by starvation
Project terminates because resources run out
Termination by extinction
Terminated by senior management because project failed (Objectives not met, not profitable)
Why not closed properly?
Decreasing interest by team members
Cost of performing closure activities
Underestimation of how fast know-how can get lost
Importance?
System installation
Training of end users
Documentation and archiving project
Lessons learned
Project Manager Role in Closure?
Ensure all project deliverable have been completed and formally accepted by custome
Conduct project close-out meetings; both internal and external
Brainstorm to know what went wrong and right in project
List ideas for improvements
List ideas for ensuring that what went right happens again
Recognize the accomplishments of individuals
Write final project closure report
Documents and share lessons learned
Project Closure Analysis
Key: To learn from project and apply to next one for improvement
General and process related information
General information about project, the final quality, the process used and derivations
the estimated and actual start and end date