Project Closing

[e1]

Wonder if any of you have a kind of check list of all the items that you have to do when closing a project.

e.g.
check deliverables
check schedules and expenses variance etc etc
==================================================
e1
moderator of PMCert@Yahoogroups.com

 

[ponderworks]

Hi,

I usually go back to the SOW and create a checklist based on the promised deliverables and any scope changes. Then I add any promised documentation or other items not specifically in the SOW. Lastly, I add any remaining issues from acceptance testing (usually from the issue logging system we are using) and internal admin stuff like arranging for signoff of the final acceptance, reassignment of personnel, items related to warranty (if any), etc.

et

 

[e1]

Thanks for your answer.
Beside deliverables, I am also looking at the Quality Control aspects. How do you measure customer satisafction, project team opinion poll and lessons learnt.

 

[ponderworks]

Hi,

Sorry it has taken so long for me to chime in. For customer sat, etc, the easiest thing to do is a survey. For examples of quality surveys, check out...

http://www.google.com/search?sourceid=navclient&q=quality+survey

I also use surveys as a requirement in client training that is offered as a deliverable. A positive result on the survey allows me to defend to the client that I delivered the training properly. It is critical that the survey be given at the end of the last day of training, then collected, compiled, report results to the client, then file it away for the future.

 

[Notbob]

Compiling some form of project team opinion poll and Lessons learnt can be achieved, in part, by asking members of the project team to put together an objective, brief review of their views on the project - where things worked, where things didn't.

It doesn't need to be anything large or all-inclusive, especially if the project team is fairly large.

Depending on the size/nature of the project team, there may be common observations or recommendations. (Once you filter out the traditional "Project Management got in our way", "Too many meetings", and so on...)

Getting input from across the team - rather than just the project management end - will help to improve project management "Best Practice" for future projects - useful for the client, department, company or consultant project manager (delete as applicable)

It's just another one of those iterative cycles of continuous improvement.

Regards,

Jon Wilson
Threespot Limited

http://www.threespot.co.uk