Closing a Project

After the planning, executing, and controlling processes of the project, the final process is the closing of the project. At this point, you’ve fulfilled the goals of the project and it’s now complete. In the closing stages of the project, you can analyze project performance with concrete data about schedule, cost, and resource use. You can also identify lessons learned and save acquired project knowledge.

Analyzing Project Performance

Review your overall project and compare your baseline plan to your actual plan. You can review variances in the schedule, in costs, and in assignment work. Any large variances can help point out problem areas in the project. Some helpful reports for such analysis include the following:

  • Project Summary

  • Overbudget Tasks

  • Top-Level Tasks

  • Overbudget Resources

  • Milestones

  • Earned Value

  • Budget

To generate one of these reports, click View, Reports and then double-click Overview or Costs. Double-click the name of the report.

Note

For more information about generating reports, see Chapter 12.

Recording Lessons Learned

Whether or not you will continue to be involved in this type of project, others are likely to benefit from the experience and knowledge you’ve gained. At the end of your project, gather your team together and conduct a "postmortem" session, in which you can objectively discuss what went well with the project and what could be improved next time.

It’s often helpful to have team members prepare notes in advance. For larger projects, you might find it more practical to conduct a series of meetings with different groups of team members and stakeholders, perhaps those who were responsible for different aspects of the project.

Be sure to have a concrete method for recording the discussion points. After the session(s), compile the lessons learned report, including solutions to identified problem areas.

If the project plan is your repository for project-related documents, add your lessons learned report to the closed project. You can embed the document in the plan or create a link to the document. Or, if you’re working in an enterprise environment with Office Project Server 2007, you can add it to the document library for the project.

Note

For more information about adding a document to a project, see the section titled Attaching Project Documentation in Chapter 3. For information about using the document library, see the section titled Controlling Project Documents in Chapter 22.

In addition to archiving the document with the rest of the project historical records, include it with your planning materials for the next project. Be sure to keep your solutions in the forefront so that you can continue to improve your project management processes.

Saving Acquired Project Knowledge

Through the planning and tracking of your project, it’s likely that you’ve recorded a mass of valuable information about the following:

  • Task durations

  • Task and resource costs

  • Work metrics (units per hour completed, and so on)

You might want to collect information about planned or actual durations, work, and costs to use as standards for planning future projects.

These durations and work metrics can be included in a project template based on the closing project. Save the project plan as a project template for future use by you or other project managers in your organization who will be working on a similar type of project. In your template, you can remove actuals, resource names, and constraint dates, for example. But the tasks, durations, task dependencies, base calendars, and generic resources can be invaluable in a project template. In addition, any custom solutions you’ve developed—such as views, reports, filters, and macros—can also become a part of your template. Through the efficiencies you built into your project plan, you’re laying the groundwork for future efficiencies.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.118.0.248