Looking through my mail today I am getting an increasing number of requests for a DIY guide to writing a Project Communications Plan. Well after a lot of thought here it is 
If you download this guide and it was of use to you please comment on the blog especially if you have any suggestions as to how it could be improved.
© Copyright 2009 Clarety Limited. All Rights Reserved
TerraCopy Could Restore Your Faith in Vista 
Down Load TerraCopy Pro
Some weeks ago my main office PC deciding to give up the ghost.
Drat & Double Drat!!
Read more...
What this is
A communications plan is possibly one of the most important project management documents. This document details how you and your team will communicate important information during the projects life cycle to your various stake holders (status, meetings, issues and , deliverables). This document will include details of your stakeholders and their relative importance in terms of influence and need for information.
Why it’s useful
A Communication Plan will detail what communication channels can be used (email, intranet, meetings) and who and how often varous stakeholders will receive such communications. Good communication delivered in the right form and at a frequency relevant to a stakeholders levels of influence and involvement in your project is key to getting stakeholder engagment.
No communications plan often means NO engagement.
How to use it
Use the outline in the sample document to create a communication plan for your project. The amount of communication may vary depending on the size of your team, number of stakeholders and the complexity of your project. One of the most important things to do before completing this document is to analyze your stakeholders. Identify who they are and match them to the communications channel and frequency of communication necessary for their successful engagement. One way to do this is to use a Stakeholder Interest Map and to develop this as part of a workshop with your team and perhaps your project board. This communications plan is one of the very best templates available on the internet.
Read more...
Once you start implementing risk and issue management for yourself you soon realise that week by week snap shots of your project /programmes risk and issue logs have their limitations. At some point you will want to identify and report on long term risk and issue management trends which are proven early warning indicators of future project /programme success or failure.
Read more...
I have recently been getting a growing amount of traffic to my site from an excellent blog entitled “Stevey’s Blog Rants”.
I have also received mail from my readers recommending that I mention a particular post of Steve’s entitled “Good Agile Bad Agile”.
Despite the fact that this post is a little dated it is one of the most commented Agile posts on the net because of its open an frank discussion about the potential deficiencies of Agile. If anyone who interested in reading this warts and all discussion about the new Agile religion, then look no further. Its a very well written post casting doubt on Agile as a silver bullet development methodology /framework.
Read more...
