Concise Guide to Closing / Evaluating Projects

May 6, 2009 | Author: PM Hut | Filed under: Lessons Learned, Project Closure, Project Lifecycle Phases

Concise Guide to Closing / Evaluating Projects
By The Office of Government Commerce - OGC, UK

At the end of the project the customer organisation will want to know how well it conducted the project and whether the expected benefits have been achieved. Project closure is a formally controlled process, whether the project has completed to plan or was stopped prematurely. It is closed down on agreement by senior management to an end of project report and lessons learned report.

A post project review or post implementation review should be undertaken subsequently to confirm whether the expected benefits have been delivered and realised. This information should be fed back to senior management, as it will inform other projects underway or planned.

Successful delivery toolkit, the Office of Government Commerce - © Crown Copyright 2009

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

Related Articles

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

The Stevens Enterprise Project Management Master's Program

Project Management Categories