Page 304 - Project+

determine what went right so that you can repeat these processes on the next project.

Lessons learned review involves analyzing the strengths and weaknesses of the project
management process, the project team, and, if you dare, the project manager’s
performance.

Unfortunately, sometimes projects do fail. You can learn lessons from failed projects as
well as from successful projects, and you should document this information for future
reference. Most project managers, however, do not document lessons learned. The
reason for this is that employees don’t want to admit to making mistakes or learning

from mistakes made during the project. And they do not want their name associated
with failed projects or even with mishaps on successful projects.

You and your management team will have to work to create an atmosphere of trust and
assurance that lessons learned are not reasons for dismissing employees but are
learning opportunities that benefit all those associated with the project. Lessons
learned allow you to carry knowledge gained on this project to other projects you’ll

work on going forward. They’ll also prevent repeat mistakes in the future if you take
the time to review the project documents and lessons learned prior to undertaking
your new project.

Lessons learned can be some of the most valuable information you’ll take
away from a project. We can all learn from our experiences, and what better way to
have even more success on your next project than to review a similar past project’s

lessons learned document? But lessons learned will be there only if you document
them now.

The following is a partial list of the areas you should review in the lesson learned
session. This is by no means a complete list but should give you a good starting point.
You should document everything you learn in these sessions. Lessons learned are
included with all the other project documentation and go into the project archive
when completed.

Review each process group (Initiating, Planning, Executing, Monitoring and

Controlling, and Closing).

Review the performance of the project team.

Document vendor performance.

Examine sponsor and key-stakeholder involvement.

Review the risks that occurred and the effectiveness of the risk response plans.

Document risks that occurred that were not identified during the project.

Evaluate the estimating techniques used for costs and resources.

304