Archive for the ‘Closing Process’ Category

Moving Lessons to Lesson’s Learned

Tuesday, November 30th, 2010

Program/Project Closing Process

 

December is usually a very busy month for wrapping up programs and projects. Many organizations like to close out projects at the end of their fiscal year in order to match up projects and funding.

 

During this period, some organizations conduct project debrief sessions during the project-close process. Some project teams refer these debrief sessions as “lessons-learned” sessions.


We highly recommend having project debrief sessions after every major program and/or project.  We further recommend that our clients call these sessions “project-debriefing”, or “close-out” sessions. Why? Because what you learn from these sessions are only lessons learned if implemented or integrated into your project execution and/or managing and controlling processes.

 

We believe, at a minimum, the following five (5) questions should be asked during any project debriefing session.

 

They are:

 

1. If we had to do this project all over again, what would we do different?

 

2. What would we do the same?

 

3. If we missed any milestones, financial, scope/quality targets, why did it happen? [Secondary and Tertiary "Why" questions should also be asked.]

 

4. Were there things our project team(s) needed that we should have provided and did not? What prevented us from providing them? What were the early signs that they needed help and/or additional support?

 

5. Did we effectively communicate to our sponsors, stakeholders and/or project teams? How could these communication activities have been improved?

 

Many more questions are asked during the debriefing sessions that we lead, but these five are the bare minimum.

 

The entire project team, sponsors and stakeholders should participate in these debriefing sessions. They should be positioned as a learning/constructive criticism session not a “beat-up” session. The goal is to make the organization better. The goal is to deliver your programs and projects more effectively so the organization can realize the benefits sooner and with less organizational stress.

 

After these sessions are conducted, the program and/or project manager should develop specific action plans that are shared throughout the organization. The action plans should be categorized by when they are performed within the project and/or program. For example:

 

  • Initiating process
  • Planning process
  • Executing process
  • Managing and controlling process
  • Closing process

 

In addition, the action plans should be further categorized by project management discipline (i.e., PMBOK Knowledge Area) such as:

 

  • Project integration management
  • Project scope management
  • Project time management
  • Project cost management
  • Project quality management
  • Project human resource management
  • Project communications management
  • Project risk management
  • Project procurement management

 

After these actions have been integrated into your program and project management processes for future projects, then you can accurately call these “lessons learned”. Until then, they are ideas, concepts and potential learning.

 

Ask these questions during your project debriefing sessions and ensure your organization has specific and measurable action plans implemented as a result of these sessions. You will be amazed at how quickly your organization improves project quality on your future programs and projects.

Share and enjoy this Hendon Group article:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Add to favorites
  • LinkedIn
  • RSS
  • Twitter
  • Yahoo! Buzz

Posted in Closing Process, Leadership | No Comments »

Closing Process – Are you providing feedback to your team members?

Monday, December 14th, 2009

Background

Project Management Institute’s (PMI) A Guide to The Project Management Body of Knowledge (PMBOK), Third Addition describes the Closing Process Group to include the processes “used to formally terminate all activities of a project or project phase, hand off the completed product to others or close a cancelled project” (p.66).

Challenge

A common activity that is not consistently performed (hopefully not intentionally ignored) by Program and Project Leaders is providing formal feedback to each of the team members at the end of a program and/or project.

Helpful Hints

Some organizations have formal performance appraisal and professional development programs. Many do not. However, whether your organization does or does not have formal programs, as a Program / Project Leader, you should take the lead and make sure you provide your team members formal feedback. Your team members benefit by having concrete dialog on how they could have been more effective and efficient…and, how they can grow.

The benefit to the organization is the organization saves cost with organizational learning and not having to relearn the lessons that slowed down the program / project the first time around. Organizational learning also saves the program/project schedule duration (for the same reason). Improved schedule duration allows organizations to rollout their program/project to the marketplace sooner and improve their competitive advantage position.

So, the next time you close out a program and/or project, have the dialog with your team on how they could have been more effective (and efficient). Your team members will thank you. Your organization will thank you.

Ira M. Hendon, PMP®
President and CEO
Hendon Group, Inc.

References

Project Management Institute (2004). A Guide to the Project Management Body of Knowledge (3rd ed). Newtown Square: Project Management Institute.

– © Copyright 2006 – 2009 Hendon Group, Inc.  All Rights Reserved.

Share and enjoy this Hendon Group article:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Add to favorites
  • LinkedIn
  • RSS
  • Twitter
  • Yahoo! Buzz

Posted in Closing Process | Comments Off