Directions for using template:
Read the Guidance
(Arial blue font in brackets) to understand the
information that should be placed in each section of this template. Then delete
the Guidance and replace the placeholder within <<Begin text here>>
with your response. There may be additional Guidance in the Appendix of some
documents, which should also be deleted once it has been used.
Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size:
You may elect to indent sections for readability.
| |
Author Position |
|
|
Ó 2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Microsoft and Visual Basic are either registered trademarks
or trademarks of Microsoft in the
Change Record
Date |
Author |
Version |
Change Reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
Name |
Version Approved |
Position |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
Name |
Position |
|
|
|
|
|
|
|
|
Document Properties
Item |
Details |
Document Title |
|
Author |
|
Creation Date |
|
Last Updated |
|
[Introduction to the Template
Description: The Communication Plan describes how the project will
establish a reliable means of assuring visibility and co-operation by
communicating status and news about the project to all appropriate stakeholders.
It describes:
·
The communications rules to be applied
·
The organizational matrices of communications and
meetings
The Communication
Plan identifies the processes, methods, and tools required to ensure timely and
appropriate collection, distribution, and management of project information for
all project participants.
Justification: Effective communication among the project teams and with
the customer ensures that all project participants are well informed and have
the necessary information from which to make decisions. The results of effective
communication include:
·
More accurate specifications and plans are built
·
Discrepancies between the components of the solution are
minimized
·
Proper expectations for external parties are set
All team members
have communication responsibilities.
{Team Role Primary: Product
Management is primarily responsible for the communication plan. This role
facilitates communication between decision makers among the project and between
the project and external parties.
Team Role Secondary: Program Management, Development,
Test, User Experience, and Release Management all need to understand the
communication plan as a success factor of the project. This sets appropriate
expectations and provides avenues for communication between team members.}]
[Description: Provide an overall summary of the contents
of this document.
Justification: Some readers may need to know only the plan’s highlights,
and summarizing creates that user view. It also enables the full reader to know the
essence of the document before they look at the details.]
[Description: The
Objectives section identifies the purpose of the plan in terms of what the
project’s communication process is to accomplish. Communication objectives may
include subjects such as timeliness, security, breadth of communication, etc.
This section may also contain a description of the environmental conditions that
demand specific communication approaches and objectives.
Justification: Identifying Communication Objectives ensures that the
team has carefully considered the project’s situation and created an appropriate
communication approach.]
[Description: The
Confidential and Sensitive Information section provides general guidance on
disclosing information. It should identify any specific project members who will
provide direction in this area when questions arise.
Justification: Certain project and/or technical information may be
confidential or sensitive to the project or to certain persons or companies
within the project. Care should be applied to not divulge such information.]
[Description: The Internal
Reporting section identifies the mechanisms and organization structure for
normal and ad hoc project reporting.
Justification: Clear articulation of communication responsibilities
ensures that information is created and distributed to support efficient project
activity.]
[Description: The
Internal Communication Map identifies audience, information subject,
communication method, communication timing/frequency, and originator. This map
can be developed in the form of a matrix.]
<<Begin text here>>
[Description: The
Project News and Briefings section describes how ad hoc communication that
doesn't fall into the defined communication map will occur. This includes news
bulletins or subject specific briefings.]
<<Begin text here>>
[Description: The
External Communication section identifies how communication will occur with any
external organizations not directly involved with the project. Do not include
organizations that have signed Non Disclosure Agreements.]
<<Begin text here>>
[Description: The Publicity section describes any
anticipated or planned publicity for the project. It identifies the nature of
the information and its audience. This section should also include a description
of the approach taken for externally originated.]
[Description: The External Inquiries section provides
guidance on how external contacts should be handled. This includes the
identification of the primary person to whom all external inquiries should be
passed.]
<<Begin text here>>
[Description: The
External Communication Map identifies audience, information subject,
communication method, communication timing/frequency, and originator. This map
can be developed in the form of a matrix.]