To Have and To Hold

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog


View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Roberto Toledo
Vivek Prakash
Cyndee Miller
Shobhna Raghupathy
Wanda Curlee
Rex Holmlin
Christian Bisson
Taralyn Frasqueri-Molina

Recent Posts

7 Ways to Align Portfolio Management with Strategy

Give Up Power to Lead the Team - Part 2

The Common Sense of Risk and Opportunity

How Does OPM Fit In?

Meet the Culture Change Challenge With These 3 Tips

In one of my previous posts, I suggested ways to maintain documentation. And as you know, documentation is very important -- it's the essence of knowledge transfer. The beauty of documentation is that it allows us to avoid the pains of reinventing a series of events that may only reside in a person's mind as a singular experience. It can also lead us to extract some aspect that may move our project from uncertainty and unknowns to more useful information. 
So, once we have taken the precautions I mentioned in my previous post for generating clear and valid documentation, the question becomes: What project documentation should we always have and hold on to? I would suggest, at a minimum, the following:

The charter. It is the closest disclosure to everything the project should touch on. It includes a high-level look at the project: resource list, budget, timeline, assumptions, constraints, risks, other areas of impact and dependencies, a brief description and an immediate focus.

Budget background and expenditures. This information typically details the budget spending and directs you to possible future support, if any can be used again.

Sources. These include contacts and stakeholders; where information is stored; direct lines of contact; contacts who would be next in the succession; who and where to reach out to in case of additional needs; and where information stemmed from, and how it should be categorized and even prioritized.

A status report of risks and issues in their most recent form. These items show the progress that has or has not been made and is especially helpful in communicating to a new project manager (or yourself, if returning to a project) where to pick up. This status report can even help determine the project's resource needs.

Scope. This tells you what should have been the focus of the project. It also helps determine whether there needed to be an extension to this scope or if something different should be embarked upon, such as a total new project or maybe a revamping of the current scope.

Are there any types of documentation you find significant to have during a project and to hold on to after a project closes?
Posted by Bernadine Douglas on: August 28, 2014 12:35 PM | Permalink

Comments (5)

Please login or join to subscribe to this item
Very good article.

Hi Drake, thanks. Please share some documents you find helpful. Bernadine

Contracts and agreements.
Lessons learned.

I 2nd Ann Savage's comment! :-)

I 2nd Ann Savage's comment! :-)

Please Login/Register to leave a comment.


"If you think you can, you can. And if you think you can't, you're right."

- Mary Kay Ash

Test your PM knowledge