A well planned project has a well planned Communication strategy. The following are guidelines and options when creating a Project Communication Plan.
|What |Who/Target |Purpose |When/Frequency |Type/Method(s) | |Initiation Meeting |All stakeholders* |Gather information for Initiation Plan |FIRST |Meeting | | | | |Before Project Start Date | | |Distribute Project Initiation |All stakeholders* |Distribute Plan to alert stakeholders of project |Before Kick Off Meeting |Document distributed via hardcopy or | |Plan | |scope and to gain buy in. |Before Project Start Date |electronically. May be posted on project| | | | | |website or OIT Blackboard site. | | | | | |PPM Templates: Project Snapshot or “Lite”| | | | | |Initiation Plan | |Project Kick Off |All stakeholders* |Communicate plans and stakeholder |At or near Project Start Date |Meeting | | | |roles/responsibilities. | | | | | |Encourage communication among stakeholders. | | | |Status Reports |All stakeholders and Project |Update stakeholders on progress of the project. |Regularly Scheduled. |Distribute electronically and post via | | |Office | |Monthly is recommended for large/midsize projects. |web/OIT Blackboard site. | | | | | |PPM Template: Status Report | |Team Meetings |Entire Project Team. |To review detailed plans (tasks, assignments, and |Regularly Scheduled. |Meeting | | |Individual meetings for |action items). |Weekly is recommended for entire team. Weekly or |PPM Template: Detailed Plan | | |sub-teams, technical team, and| |bi-weekly for sub-teams as appropriate. | | | |Functional teams as | | | | |...
Please join StudyMode to read the full document