• Authors

  • Calendar of Posts

    November 2011
    M T W T F S S
    « Oct   Dec »
     123456
    78910111213
    14151617181920
    21222324252627
    282930  
  • Enter your email address to follow this blog and receive notifications of new posts by email.

    Join 7 other followers

Lessons learned notes

Lessons learned are a collection of things that went right, things that went wrong, and things that should be done differently. They can be collected at the end of each phase, and at the end of the project. (Mulcahy 32)

Lessons learned should include technical aspects of the project, tying them to reality. They should look at project management, including planning and risk prevention. And they should look at management, including communication. (Mulcahy 32) The documentation looks at the causes of the issues, the reasoning behind the corrective action (PMBOK 261).

Lessons learned should be shared throughout the organization, probably through a PMO, or whatever the existing structure for sharing this information is.

During the initiating phase, lessons learned from other projects should be reviewed as part of identifying risks. They should be certified during the Closing phase of the project, and stored.

I had identified back a few weeks ago that I would be conducting a lessons learned exercise for a CRM project I was working on. That exercise is finally scheduled for next week.  More to come.

Advertisements
Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: