• Authors

  • Calendar of Posts

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

    Join 7 other subscribers

Closing Process Group

Finally, finally, we’ve gotten to the fifth process group of the 5. Closing. This is the shortest list of steps. This is the one no one likes. This is the one that gets the short shrift (and you thought Planning was undervalued!).

We close the project now. We verify the work was done, and done to the original requirements. We close the procurements, and sign off on those. We sit down with our customers and make sure they agree with us that the original requirements were met, and that the changes were implemented as approved. We DOCUMENT that they sign off on this. We store all of the documents and lessons learned in a single location, so that when you start the next, similar project you have some historical process to refer back to in the  Initiation process group.

Then, we wipe our hands of it. Operations takes over the running of the unique, shiny new thing that was built with the project, and we send our project team back into the wilds from whence they came (Mulcahey, PMP Exam Prep, 6th Edition, 43).

I think it’s this last 2 portions that I most dislike about the Closing process group. I always feel that the deliverable widgets don’t look all shiny and new, or like they’re half-formed, and giving them to Operations, they are going to not appreciate them.

Then, with the releasing of the team, it means that the PM (me) gets released too. Then, you are left with this impression that Ops didn’t like your results, and no one will ever assign you to a project again. And then Monday rolls around…