Communication Plan
Essay Preview: Communication Plan
Report this essay
Communications Plan (PDLC)
Document Information
Software Version:
Publication Date:
Catalog Number:
Creation Date:
20 September, 2005
Contents
Introduction
Purpose and Scope
Related Documents
Terms and Definition
Key Roles and Responsibilities
Quality Assurance Responsibilities
PDU OBS/Focal Point List
Coordination Meeting Plan
Purpose and Scope
Recurring Coordination Meetings
Event-Driven Coordination Meetings
Reporting Plan
Purpose and Scope
Communications Report List
Open Issues and Action Items
Purpose and Scope
Organization of AIs and OIs
User instructions are presented in green against a light-yellow background.
To delete a user instruction section, select the user instruction section by clicking to the left of the shaded area, and then press CTRL+X.
INTRODUCTION
Purpose and Scope
Proactive communication is important on all projects. The program manager must make sure that team members, customers and stakeholders have the information they need to do their jobs. Communication is also a vital way to manage expectations about how the project is going and who needs to be doing what. This can be as simple as talking to your team members about how they are doing on their assigned work, or a regularly scheduled status meeting. However you do it, proper communication can go a long way toward ensuring project success.
Communication gets much more complex the larger a project gets, and the more people that are involved. Larger projects require communication to be planned in advance, taking into account the particular needs of the people involved. This is where a Communication Plan is useful. A Communication Plan allows you to think through how to communicate most efficiently and effectively to the various constituents.
Effective communication means that you are providing information in the right format, at the right time and with the right impact.
The Communications Plan encompasses all the decisions and preparations required to set up a system of communications that will support the release/projects activities throughout the release life cycle.
The plan includes the following components:
■
Key roles and responsibilities
■
PDU organizational breakdown structure (OBS)/Focal Points list
■
Coordination meeting plan
■
Status reporting plan
■
Action item/Open Issue management plan
Each of the following chapters is devoted to one of the elements in the above list.
The plan refers to the communications within and between the internal PDU forums and groups and externally with other organizational units and/or forums as described in this document.
Related Documents
■
Communications Procedure
(PCDOCS #225069)
Terms and Definition
Definition
Forum Manager
A manager who is assigned the responsibility of managing the forum and ensuring that the related processes and activities are performed. This includes but is not limited to; maintaining the AI/OI repository, and identifying the AI and or resolve OI.
Release Manager
Program manager responsible for consolidating schedules, commitments, and status provided by project core teams.
Project Core Team
Group of representatives from each functional group responsible for a particular project, such as product management, program management, development, PQA, and tech pubs. Each team member is responsible for raising issues from within the group they represent and forwarding information relevant to others in their functional team.
Release Core Team
One person from each functional group to represent all project core teams for that group. In addition, a person from CM, manufacturing, training, readiness, and advocacy engineering is also included.
Review Manager
A manager who is assigned the responsibility of managing and performing the entire review process and related activities for a particular document or set of documents.
KEY ROLES AND RESPONSIBILITIES
THE FUNCTIONAL AREAS ARE:
Core Team – Required attendance by member or delegate
■
Core team lead (program manager)
■
Product management
■
Application design
■
Application development
■
Foundation development
■
■
Technical publications
CORE TEAM STAKEHOLDERS – INVITED TO TE CORE TEAM MEETINGS BUT MAY BE OPTIONAL
■
Customer care readiness
■
PSO readiness
■
Training
■
Demo development readiness
■
Configuration/Manufacturing
■
Advocacy engineering