It is important in a project to keep very good documentation.

It should be complete, organised, and easy to search (not unorganised folders on lots of team members desks where no on knows where parts are).

• This improves the projects legal standing.
• Reduces miscommunication problems.
• Clarifies scope, variations, design, etc.
• Allows team members to easily find and access project information (without having to go around asking other team members)
• Allows new team members or a replacement project manager to join the project easier.
• Reduces wasted time.
• Allows audits to run smoothly (I find that if your documentation is properly organised the auditors give you a lot less hassle, and you get a good audit report).

Tagged with: Documentation

Filed under: Documentation

The title says it all.

Document all communication with your client (and with suppliers and contractors).

• Even with friendly or familiar clients.

• Client’s project manager may change, so verbal agreements won’t be recognised.

• Possibly use an incoming and outgoing correspondence log.

Tagged with: Communication • Documentation

Filed under: Documentation

Document all changes, variations, agreements etc. If it is done verbally, put it in writing and send to the person involved. Make sure the client / stakeholder is sent this documentation.

• This will protect yourself and your company in the event of disagreement or a claim.
• It will clarify intentions.
• Important for QA documentation, and for scope adherence, and legal.
• Get approval in writing for changes or variations.
• Document on the assumption that “if it’s not in writing, it didn’t happen”.
• At least prepare a written confirmation of verbal instructions and copy to the client.
• Document your efforts to meet client goals.
• Get and distribute copies of minutes of meetings with the client.

Tagged with: changes • Documentation

Filed under: Documentation