PROJECT COMMUNICATION PLAN
[Save file name as: client name COMMUNICATION PLAN yyyymmdd]
Client Name:
|
|
Title:
|
|
Project:
|
|
Date:
|
|
Project #:
|
|
Version:
|
Template 1.1 / Document 1.0
|
INTRODUCTION
Overview
Overview
Assumptions and constraints
Definitions and acronyms
Reference materials
Project Sponsor
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
Customers
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
External Stakeholders
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
Internal Stakeholders
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
Project Manager
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
Project Team Members
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
Consultants/Subject Matter Experts (SMEs)
Name
|
Title, Department, Organization
|
Contact Information
|
Project Roles and Responsibilities
|
|
|
|
|
REVIEWS AND APPROVALS
Milestone / Deliverables Required
|
Target Date (if any)
|
Review Responsibility
|
Approve Responsibility
|
|
|
|
|
COMMUNICATION AND CONTROLS
Type of Information
e.g. Status Report etc
|
Format of Information (Medium)
e.g. Written, Meetings etc
|
Information Exchange Schedule (Target Date or Frequency)
|
Recipient of Information (Distribution Group or Attendees)
|
Description of Information (Details)
|
|
|
|
|
|
Methods used to gather and store various types of information.
Accessing Information
Methods for accessing information between scheduled communications
Escalation Threshold
A graphic representation of the project team’s discretion on managing the project cost and schedule variances. The area drawn by the sponsor indicates the variance from the project baseline that can be encountered and managed independently by the project team without report to the project sponsor.
APPROVALS
We, the undersigned, accept the Communication Management Plan, as a stable work product to be placed under formal change control.
CLIENT APPROVAL CYBERNET APPROVAL
________________________________ ________________________________
Client Signature CyberNet Signature
________________________________ ________________________________
Printed Name Printed Name
_____________ _____________
Date Date