Submitted by labraham on December 16, 2009 - 7:46pm.When you are running a program, there is typically a lot of paperwork involved. Project plans, dashboards, risk sheets, resource sheets, requirements documents, design documents, test plans, budgets, etc... And there will be multiple revisions of each for each component of your program. The amount of paperwork involved would probably kill a small forest, if you attempted to print it all out. And keeping track of the latest versions of this information can be a nightmare for even the most diligent program manager, let alone the people working in the individual components.
That's why it's important to start the project with a firm method of information exchange established. In most cases, you are going to want to leverage a document repository or information share like a Sharepoint portal or a Wiki. That's because they provide you with a central repository for all the documents and have built in version control features that you can take advantage of. Whatever you decide to use, make sure that it is setup and ready by the time you start your program, or you will miss capturing the valuable assumptions and details that always emerge at the start of work.
Having your information repository won't stop people from emailing documents to each other and having multiple versions on their desktop. But it will mean that everyone will know exactly where to go for the latest, most authoritative information on the program.
Trackback URL for this post:
http://www.allianceglobalservices.com/trackback/519
from AGS on December 18, 2009 - 11:24am
|
Recent comments
9 weeks 2 days ago
12 weeks 6 days ago