Communication Plan
Scope
This document serves as basis for agreeing the flowing of information within all stakeholders. The2se are the elements to be fixed during the “Definition” phase (see post).
- What. The information to be delivered (either sent or received)
- Who. The person accountable for delivering the “correct” information (see post)
- When/How. The schedule arranged for making the information available and the media to be adopted (e.g. publication on the web site).
- Which. The template (process) to be used for delivering the information.
Most of these data are in the “Communication strategy management report” . The target for this activity is the acceptance of the processes used for distributing information during all the phases of the project. Due to the unique nature of the project, this document should be reviewed, especially during or after any eventual crisis that would need special arrangements.
An important caveat (costs of resources allocation)
The management (production, controlling, distribution and consumption) of any document absorbs some energy/time. It is important that this aspect is correctly worked out and accepted, this will avoid any problem about the resource allocation.
Quality
The effectiveness can be measured with these parameters:
1) This document should be signed by all accountable stakeholders.
RACI (who does what)
| Operation desc./Roles [1] | Spr | PM | BA | SME | TL | Prd | Stkhd |
| Preparing the communication map matching the stakeholders (from the information possession viewpoint) to the available templates |
C |
A |
R |
C |
I |
I |
C |
| Agreeing all the formats and methods |
C |
A |
R |
C |
I |
I |
C |
| Compiling the Report |
C |
A |
R |
I |
I |
I |
C |
| Verifying the quality, especially during the crisis management |
C |
A |
R |
I |
I |
I |
C |
Document structure
Distribution list
This kind of information has to be made publicly available (read-only).
Registrar section
All “standard” information (e.g. date, version etc) are described in the following post
These are the key fields
| Communication Plan ID | |
| Process involved | e.g. Risk, Stage, Issue etc. |
| Description of information required | Brief and clear definition of what has been agreed to supply / discuss. |
| Template reference | Which is the used version of the chosen template |
| Schedule | To be matched with the available revenue |
| Media | |
| Stakeholders involved | See relevant register |
Technical domains
Financial / Commercial domains
1) Resource allocation
Notes
References
[1] Spr Sponsor, PM Project manager, BA Business Analyst, TL Technical Leader, Prd Producer, Stkhd Stakeholder

