Professional Documents
Culture Documents
Manual 10-Project Communication Management-Book 1
Manual 10-Project Communication Management-Book 1
Project Communication
Management
Book 1 of 3
Communication Planning and Management
Manual 10: Project Communication Management
Contents
Topic 1: Communication Planning and Management 3
Section A: An Overview of Communication Planning 3
Communications Planning 3
Communications Planning: Inputs 3
Organizational Process Assets 3
Project Scope Statement 3
Project Management Plan 4
Communications Planning: Tools and Techniques 4
Communications Requirements Analysis 4
Communications Technology 4
Communications Planning: Outputs 6
Communications Management Plan 6
Section B: Communications Planning Inputs 7
Communications Requirements 7
Special Considerations 7
Communications Technology 8
Constraints 8
Assumptions 8
Section C: Communications Planning Tools and Techniques 9
Stakeholder Analysis 9
Components of Stakeholder Analysis 9
The Five Fundamental Questions 9
Communications Interfaces 10
Section D: Communications Planning Outputs 14
The Communications Planning Matrix 14
Alternate Communications Planning Matrix 15
Project Communication Tools 15
Project Documents Used in Process Groups 16
Roles/Responsibilities of Stakeholder 16
Defining Communications Planning 17
Inputs, Tools and Techniques, and Outputs of Communications Planning 17
Inputs 18
Communications Requirements 18
Communications Technology 18
Constraints 18
Assumptions 18
Tools and Techniques: Stakeholder Analysis 18
The Communication Management Plan 19
Communications Planning Matrix 19
Section F: Project Communications Management 20
Project Communications Management Processes 20
Section G: Communication Management Skills 21
Dimensions of Communicating 21
Communications Concepts 21
Communications Interfaces 21
Topic 1: Communication
Planning and Management
Section A: An Overview of Communication
Planning
Communications Planning
The Communications Planning process determines the information and communications needs of the
stakeholders; for example, who needs what information, when they will need it, how it will be given to
them, and by whom. While all projects share the need to communicate project information, the
informational needs and methods of distribution vary widely. Identifying the informational needs of the
stakeholders and determining a suitable means of meeting those needs is an important factor for project
success.
On most projects, the majority of Communications Planning is done as part of the earliest project phases.
However, the results of this planning process are reviewed regularly throughout the project and revised
as needed to ensure continued applicability.
Communications Planning is often tightly linked with enterprise environmental factors and organizational
influences, since the project’s organizational structure will have a major effect on the project’s
communications requirements.
While all of the assets are used as inputs for this process, lessons learned and historical information are
of particular importance. Lessons learned and historical information can provide both decisions and
results based on previous similar projects concerning communications issues.
The project scope statement provides a documented basis for future project decisions and for confirming
a common knowledge of project scope among the stakeholders. Stakeholder analysis is completed as part
of the Scope Definition process.
The project management plan provides background information about the project, including dates and
constraints that may be relevant to Communications Planning.
• Constraints. Constraints are factors that can limit the project management team’s options. Examples
of constraints include team members situated in different geographic locations, incompatible
communication software versions, or limited communications technical capabilities.
• Assumptions. Specific assumptions that affect Communications Planning will depend upon the
particular project.
The analysis of the communications requirements results in the sum of the information needs of the
project stakeholders. These requirements are defined by combining the type and format of information
needed with an analysis of the value of that information. Project resources are expended only on
communicating information that contributes to success, or where a lack of communication can lead to
failure. This does not mean that “bad news” should not be shared; rather, the intent is to prevent
overwhelming stakeholders with minutiae.
The project manager should consider the number of potential communication channels or paths as an
indicator of the complexity of a project's communications.
The total number of communication channels is n(n-1)/2, where n = number of stakeholders. Thus, a
project with 10 stakeholders has 45 potential communication channels. A key component of planning the
project's communications, therefore, is to determine and limit who will communicate with whom and who
will receive what information. Information typically required to determine project communications
requirements includes:
• Organization charts
• Project organization and stakeholder responsibility relationships
• Disciplines, departments, and specialties involved in the project
• Logistics of how many persons will be involved with the project and at which locations
• Internal information needs (e.g., communicating across organizations)
• External information needs (e.g., communicating with the media or contractors)
• Stakeholder information.
10
Communications Technology
The methodologies used to transfer information among project stakeholders can vary significantly. For
example, a project management team may include brief conversations all the way through to extended
meetings, or simple written documents to material (e.g., schedules and databases) that is accessible
online as methods of communication.
• The urgency of the need for information. Is project success dependent upon having frequently
updated information available on a moment’s notice, or would regularly issued written reports
suffice?
• The availability of technology. Are the systems already in place appropriate, or do project needs
warrant change?
• The expected project staffing. Are the proposed communications systems compatible with the
experience and expertise of the project participants, or is extensive training and learning required?
• The length of the project. Is the available technology likely to change before the project is over?
• The project environment. Does the team meet and operate on a face-to-face basis or in a virtual
Book 1 of 3: Communication Planning and Management Page 4 of 22
Manual 10: Project Communication Management
environment?
The communications management plan is contained in, or is a subsidiary plan of, the project management
plan. The communications management plan provides:
The communications management plan can also include guidelines for project status meetings, project
team meetings, e-meetings, and e-mail. The communications management plan can be formal or
informal, highly detailed or broadly framed, and based on the needs of the project. The communications
management plan is contained in, or is a subsidiary plan of, the overall project management plan. Sample
attributes of a communications management plan can include:
Communication Planning often entails creation of additional deliverables that, in turn, require additional
time and effort. Thus, the project’s work breakdown structure, project schedule, and project budget are
updated accordingly.
• Communications requirements
• Communications technology
• Constraints
• Assumptions
Communications Requirements
Definition: Communications Requirements
“Communications requirements are the sum of the information requirements of the project
stakeholders. Requirements are defined by combining the type and format of information
required with an analysis of the value of that information.”
Communications requirements combine the type and format of information required with an analysis of
the value of that information. This book identifies information typically used to determine requirements:
Special Considerations
Below are some special circumstances that should be considered when planning and executing project
communications:
Site access or tours: Some projects may need to plan for public tours during project execution. Such
tours should be very carefully planned, both for safety reasons and to ensure that the tourists do not get
the wrong impression about the project. A large-scale construction project, although carefully planned
and executed, may appear chaotic to the untrained eye.
Regulatory requirements: Some projects have special communication requirements based on laws and
regulations. For example, many environmental cleanup projects have stringent requirements for public
notification and comment on proposed cleanup plans. As another example, medical device and drug
development efforts have equally stringent requirements for communicating with the relevant health
regulatory agencies.
Emergencies and accidents: Incidents that result in injuries to workers or the release of hazardous
materials into the environment almost always require special (and immediate) reporting to state and local
health, environmental, and labor agencies. Many such reporting requirements carry severe penalties for
delayed reporting.
Marketing communications: Project development or marketing projects may have very specialized
requirements for keeping potential customers informed of upcoming product features and delivery dates.
Changes over life cycle/special situations: Project events may dictate special situations where waiting for
the next official communications status report window is not adequate. Often, project changes signal a
need for more frequent communications.
Communications Technology
Communications technology is the tools, networks, and equipment within an organization used to transfer
the information back and forth among stakeholders. There is a wide variance of technology capability and
infrastructure from organization to organization, based on factors such as:
The project manager must not only consider technology capabilities within the organization, but
capabilities between organizations that the project will interface with. Another key consideration is
utilization of communications technology. Although certain communications technology may be in place at
an organization, it does not indicate that these technologies are used, or used effectively.
Depending on the organizational structure, there may be complex communications networks and rules in
place. The project manager should explore all of these aspects to identify requirements unique to the
organization’s needs. Project resources should only be expended to communicate critical information that
contributes to project success or where the lack of communication can lead to failure.
Constraints
Constraints are factors of limitation, which impact communications. In addition to technology constraints,
a key constraint is time. Timing for communications to be effective is critical for project success. This
becomes a greater challenge when a project manager manages a project across time zones.
Assumptions
Assumptions are factors that, for planning purposes, are considered to be true, real, or certain. They
include:
• Immediacy of the need for information: How frequently is information needed to ensure success and
control?
• Expected project staffing: How do the communications needs change as the project team is
expanded to include more people, people with varying skills, and people at different levels in an
organization?
• Length of project: How will communications requirements change over the life of the project?
Definition: Stakeholder
Individuals and organizations that are actively involved in the project, or whose interests may be
positively or negatively affected as a result of project execution or project completion. They may
also exert influence over the project and its results.
• Identify stakeholders
• Relationship to project
• Influence over project
• Hierarchical relationship to project
The project manager needs to consider and answer five fundamental questions. These questions should
be answered for each internal and external stakeholder group:
In short, everyone involved in the project has information requirements that need to be worked into the
communications management plan.
Communication audiences include all project stakeholders. Timeframes, methods, formats, level of detail,
and emphasis may differ, according to stakeholder. All stakeholders need some level of ongoing contact
with the project. In preparing the communications plan, it is important not to overlook anyone.
• Project stakeholders, internal and external, need and expect some communication from the project
manager and the project team.
• Project staff members need to know their duties, responsibilities, and authorities, and how they are
performing.
In short, everyone involved in the project has information requirements that need to be worked into the
communications plan.
Communications Interfaces
Project managers are found at the center of a communications web and must communicate with people in
various roles:
Top
Managers
Project
Team
Members
The analysis of the project’s information needs begins by considering the information needs of each
stakeholder, both internal and external. Although there are a myriad of things that need to be
communicated when planning and executing a project, the following topics are especially important:
a. Expectations and plans for technical quality, budget, cost, and schedule. Everyone involved in the
project must know his or her roles, responsibilities, and duties. The project plan must be clear to
everyone.
b. Risks and controls must be communicated to stakeholders, including plans implemented to mitigate
them.
c. Status and issues indicating the progress of the project should be communicated, including any
outstanding issues that need to be resolved; some issues may relate to the job duties of any individual
project team member, or they may be project-wide issues that the entire project team must be
concerned with.
d. Changes and their impacts must be appraised and communicated to the project team and
stakeholders.
e. Lessons learned should be captured when the project has been completed to further the
development of their organization’s project management system.
How often the project manager communicates depends on various factors. The project manager must
consider each stakeholder group’s need for information to consider frequency.
Considerations include:
• Information availability: How often is the information available? For example, cost performance data
may only be available on a monthly basis after invoices and time sheets are processed.
• Current firm practices and procedures: Special organizational requirements may exist for
reporting.
• Contractual obligations: It is common for contracts to specify what kinds of reports are required and
at what intervals.
• Project events and status: The expected project execution schedule may influence the choice of
reporting. Riskier events may dictate more frequent reporting in order to maintain tight control of
project cost and schedule.
• Confidence in staff and subcontractors: Managers should monitor the progress of inexperienced
staff or new subcontractors more frequently until assurances exist that these staff members have the
skills and experience to perform successfully
Very simple projects with low risk may reduce these communication guidelines.
Different methods of communication have unique characteristics, making them more (or less) appropriate
for certain types of situations. Each method should be clearly stated in the communications management
plan.
Face-to-face communication, memos, and meetings all have unique characteristics that may make them
appropriate for certain types of situations and should be spelled out in the communications management
plan.
• Information availability: Some data might not be available in one format or another, or is most
efficiently communicated in certain ways. For example, if a quality problem exists in a software
program, it could be described in writing, or the user could try the software to experience it firsthand.
• Technology availability and shortcomings: Technologies utilized must be efficiently available to both
the project manager and whomever he is communicating with. For example, telephone conversations
may be limited due to different time zones.
• Frequency requirements: Quarterly reports may be too far apart for a six- month, high-risk, high-
stakes, product prototype project.
• Need for face-to-face relationship building: Stakeholder relations may dictate more face-to-face
meetings than would be necessary in order to build and sustain a productive working environment.
• Project status: Project events may dictate the frequency of communication. Waiting until the next
official reporting cycle may be too late.
• Stakeholder preferences: Need for human contact, trust, comfort, delicate information, and
negotiation.
To be successful, the project manager’s communication pattern must meet the needs (and preferences) of
the stakeholders. To accomplish this, it often requires the project manager to use communications
methods that are not a personal preference.
Project communication needs do not remain static over the life of a project. They depend upon, and
change, based on project risk and varying levels of confidence in the abilities of the project staff or
subcontractors. For example, a great deal of confidence may exist for the design staff, so reporting is kept
to a minimum during design in order to maximize their productivity. However, if less confidence exists for
the implementation team, progress is monitored more frequently.
As a rule of thumb, as risk increases, so should communication and, more specifically, should the amount
of face-to-face communication. The project manager should plan for, and adapt, the communications
strategy based on project risk. As risk increases, project monitoring, reporting, and control should also
increase.
• A collection and filing structure for methods of gathering and storing information
• A distribution structure that details what information will flow and what methods will be used to
distribute the information
• Information to be distributed, including format, content, level of detail, and conventions/definitions
• Production schedules showing when each type of communication will be produced
• Methods for accessing information between scheduled communications
• A method for updating/refining the communications management plan
To organize the communications plan, project managers can use a simple communications planning
matrix. It organizes each stakeholder group and specifies what, when, and how project elements should
be communicated. The communications planning matrix is part of the overall project plan, and all or
relevant parts should be shared with the project stakeholders.
Shown below is a simple matrix for organizing the planned project communications. Once completed, it
can serve as the basis for the written plan, or even may be the plan itself.
A different form of matrix may be more appropriate, or it may supplement the stakeholder-based matrix.
The matrix shown below identifies various communications tools; filling out the matrix makes you
consider what would be the best use of each tool.
Team Meetings
Issues/Issue Log
Risks/Risk Log
Status Report
Change Requests/Change
Request
Project Plan
There are many different tools that can be used in project communications. A communications planning
matrix can help in coordinating the use of these tools.
Project charter: A signed agreement among all organizations involved in the project which includes a
summary of the project objectives and the end state. Used to get management approval for detailed
project planning. Specifies organizational responsibilities and authorities, and what resources each
organization will provide to the project. Ties resource provision to an agreed-upon, high-level schedule.
Project scope statement: A document that describes the detailed objectives, scope, and deliverables of
the project.
Project plan: A detailed document that describes what will be done, why it is being done, when it will be
done, what resources will be needed to do it, and how to measure the success of what has been done.
Change requests and approvals: Formal documentation for requesting a change to project scope, cost,
or schedule. Should include an impact statement specifying how not implementing the requested change
will impact the project.
Project archive: Collection of project documentation to allow for lessons learned and later project
modification.
Lessons learned: Causes of variances, reasoning behind corrective actions taken, other types of lessons.
Issue/Risk/Change Logs: Listing and status of issues or project risks and changes.
Phase Document
Roles/Responsibilities of Stakeholder
Another type of matrix can be used to identify what information should be communicated to each
stakeholder.
Facilitating Processes
Human Human Procurement Procurement
Quality Resources Resources
Inputs
Communications
requirements Tools and Techniques
Communications
Stakeholder analysis
technology
Constraints
Assumptions
Outputs
Performance improvements
Input to performance appraisals
Inputs
It is important to explore some of the specific inputs to communications planning. Unlike some project
processes, many of these inputs are not a result, or output, of prior processes.
Communications Requirements
Communications Requirements combine the type and format of information required with an analysis of
the value of that information. This book identifies information typically used to determine requirements:
Depending on the organizational structure, there may be complex communication networks and rules in
place. The project manager should explore all of these aspects to identify requirements unique to the
organization’s needs. Project resources should only be expended to communicate critical information that
contributes to project success or where the lack of communication can lead to failure.
Communications Technology
Communications technology includes the tools, networks, and equipment within an organization to assist
the communications function. There is a wide variance of technology capability and infrastructure from
organization to organization.
The project manager must not only consider technology capabilities within the organization, but
capabilities between organizations that the project will interface with. Another key consideration is
utilization of communications technology. Although certain communications technology may be in place at
an organization, it does not indicate that these technologies are used, or used effectively.
Constraints
Constraints are factors of limitation which impact communications. In addition to technology constraints, a
key constraint is time. Timing for communications to be effective is critical for project success. This
becomes a greater challenge when a project manager manages a project across time zones.
Assumptions
Assumptions are factors that, for planning purposes, are considered to be true, real, or certain. They
include:
• Immediacy of the need for information: How frequently is information needed to ensure success and
control?
• Expected project staffing: How do communication needs change as the project team is expanded to
include more people, people with varying skills, and people at different levels in an organization?
• Length of project: How will communication needs change over the life of the project?
The communication management plan documents the format, content, and conventions for different
communications needs during the project. It is important that the communications plan is compatible with
the organization’s capabilities and culture. This is why answering the fundamental communications
questions (who, how, when, what frequency) is critical to building a good communications plan. All, or just
the relevant parts, of the communications management plan should be shared with all stakeholders.
To organize the communications plan, project managers can use a simple communications planning
matrix. It organizes each internal and external stakeholder group and specifies what, when, and how
project elements should be communicated.
The processes of the Project Communications Management knowledge area occur across the project
process groups of planning, executing, controlling, and closing. This is shown in the following diagram. It
is important to note that some level of communications occurs in all processes and activities of project
management, but there are formal, defined, communications management processes that are performed
as part of certain process groups.
Process Group
Initiating Planning Executing Controlling Closing
Knowledge Area
Project Integration
… … …
Management
Project Scope
… … …
Management
Project Time
… …
Management
Project Cost
… …
Ma nagement
Project Quality
… … …
Management
Project Human
… …
Resource Management
Project
Communications Information Performance Administrative
Communications
Planning Distribution Reporting Closure
Management
Risk Project
… …
Management
Project Procurement
… … …
Management
Process Group
Initiating Planning Executing Controlling Closing
Knowledge Area
Project Information
Communications Performance Administrative
Communications Distribution
Planning (Facilitating) Reporting (Core) Closure (Core)
Management (Facilitating)
Communications is much more than a body of knowledge that must be acquired; it is a rich skill set, which
must be learned and practiced. The ability to communicate may be the most important skill that a project
manager possesses, and it can be a distinguishing factor between good and poor project managers. The
job of a project manager is to do work through others; thus, communication is central to success.
Dimensions of Communicating
Communications is a multifaceted discipline. Project managers must be concerned with many dimensions
of communication:
Communications Concepts
There are many communications concepts important to becoming a more effective communicator.
Knowledge of sender-receiver models assists the project manager in understanding the subtle
complexities in all communications. The choice of media can significantly impact communications.
Effective meeting management techniques should be applied so meetings are more productive. Each of
these topics is explored as part of the course:
• Sender-receiver models
• Choice of media
• Writing style
• Presentation techniques
• Meeting management techniques
Communications Interfaces
The project manager sits in the center of a communications hub. It is this central role of the project
manager that makes communication skills vital to the success of the project manager. A project
manager’s job is not to do the work of the project, but to get project work done through others. This
requires understanding the expectations from project sponsors and clients, and effectively communicating
these expectations to the project team. It also includes receiving feedback on progress from the project
team and communicating it back to the project sponsors.
Top
Managers
Project
Team
Members
Project managers are found at the center of a communications web and must communicate with the
following:
• Functional managers provide information regarding availability of resources, or changes in skills; they
receive information on the project direction
• Executives or sponsors provide direction on company policy, project parameters; they receive status
reports from the project manager
• Customers provide direction to the project manager and receive progress reports
• Project team members receive directives from the project manager and provide status reports.