Professional Documents
Culture Documents
Project Communications Management is the process of planning, collecting, storing, and updating project
information. This article is part of a PMP Study Guide that summarizes the Communications Management
Knowledge Area.
The Communications Management knowledge area that a project manager spends the most time on. In fact,
over 90% of the project manager’s time is spent on communications.
In this article, we will cover the key terms and three processes in the Communications Management Knowledge
Area.
» Manage Communications
» Monitor Communications
» Things to Remember
Key Terms
Stakeholder The project manager need to be the expert in project management, and the
stakeholders are the technical experts in what needs to be done and how it need
to be done. The project manager is the orchestra leader, and the work cannot be
done well without stakeholder involvement
Communication role » PM’s spend about 80 – 90% of their time acquiring and communicating
of PM information
» Innovative ideas
» Use a tight matrix – collocation of project team is best communication for the
team
» Prepare an agenda
» Encourage participation
» Issue minutes
General » Leading
management skills
» Communicating
» Negotiating
» Problem solving
» Inluencing organization
Name Email
Download
Communication requirements analysis determines the information needs of the project stakeholders
» Organizational charts
» Stakeholder register
» Project charter
» Project documents
» Availability of technology
» Ease of use
» Project environment
Communication model:
» Sender
» Messenger
» Receiver
Effective communications
The sender should encode a message, determine which communication method to use, and conYrm that the
message is understood. When encoding the message, the sender needs to be aware of the following
communication factors:
Communication methods
» Interactive communications
» The method is reciprocal and can involve just two people or many people
» Push communications
» The sender provides the information to the people who need it but does not expect feedback on the
communication
» Pull communications
» The project manager places the information in a central location. The recipients are then responsible
for retrieving or “pulling” the information from the location
Manage Communications
Manage Communications is the process of creating, collecting, distributing, and updating project information
according to the Communications Management Plan. This process happens during the Executing process group.
The key beneYt of this process is that it enables e]cient communications between project team members and
stakeholders.
Communication methods
» Face-to-face (most effective), meetings, video and audio conferences, email, instant messaging, etc.
» Sender-receiver models
» Choice of media
» Writing style
» Presentation techniques
» Facilitation techniques
» Listening techniques
Performance reporting
» Performance reports,
» Deliverables status,
» Schedule progress
» Cost incurred
PM Expectations
» Stakeholders’ need must continue to be met and their issues resolved throughout the project
» Make stakeholders feel that their needs and concerns are being considered
» Keeping open communication channels with the stakeholders is key so they can inform the project manager
of potential changes, added risks, and other information
Name Email
Submit
Monitor Communications
Monitor Communications is the process of analyzing communications through the project life cycle and sending
relevant work performance information to stakeholders.
» Noisy surroundings
» Hostility
» Language barriers
» Culture barriers
» Status report – this report describes where the project now stands regarding the performance measurement
baseline
» Trend report – examines project results over time to see if performance is improving or deteriorating
» Earned value report – integrates scope, cost, and schedule measures to assess project performance, using
the terms described in Cost Management section
» Lessons learned documentation – reports on performance are used as lessons learned for future projects
Things to understand:
» Reports should provide the kinds of information and the level of detail required by stakeholder
» The best way to have a report read and acted on is to use the most appropriate communication method in
sending it
» You should not spend all time reporting. Remember that many reports are just about the past. Finding
information about the past means it is too late to prevent the problem. You need to keep managing the project,
rather than just reporting on it, to make a project successful
» Report should include measurements against the performance measurement baseline set in the project
management plan. Remember that you should have performance measurement baseline (the combined scope,
schedule, and cost baselines) that can be measured. Those measurements are an indication of how
successful you are as a project manager
Things to Remember
» Identify ALL stakeholders
» Any stakeholders who are missed will likely be found later. When they are uncovered, they will make
changes and could cause delays. Changes made later in the project are much more costly and harder to
integrate than those made earlier.
» Stakeholders are Yrst identiYed as part of initiating the project, and this list is reassessed during project
execution
» The project manager must make every effort to obtain ALL the requirements before work begins
» There are many ways to make sure you have all requirements – from just asking if you do, to
conducting requirement reviews, to telling people the negative consequences to the organization and
the project if requirements are found later
» The requirements should not just relate to how stakeholders want the product of the project to
function, but should also include their communications requirements
» These are what the stakeholders expect to happen to them, and their department, and company as a
whole. They tend to be much more ambiguous than stated requirements, or they may be undeYned
requirements. They may be intentionally or unintentionally hidden
» Naturally, expectations that go unidentiYed will have major impacts across all constraints
» Stakeholders may be particularly interested in working on some part of the project, getting a chance to
learn new skills, getting a chance to prove their skills, or even getting out of working on certain parts of
the project
» A great project manager, will determine each stakeholder’s interest related to the project and attempt
to either build them into the project or implement them as reward
» To some degree, each stakeholder will be able to negatively or positively affect a project. This is their
level of inluence, and it should be identiYed and managed
» Project management focuses on planning before taking action. Since communications are the most
frequent cause of problems on projects, planning communications is critical
» Stakeholders are included in project presentations are receive project information, including progress
reports, updates, changes to the project management plan, and maybe even changes to the project
documents
» Managing stakeholder doesn’t end during initiating. They must be managed throughout the life of the
project
Name Email
Submit
Related Posts
15 Aug, 2017
! 2
Previous Post Next Post
Resources Management: PMP Study Guide Risk Management: PMP Study Guide (PMBOK 6th
(PMBOK 6th Edition) Edition)
0 Comments Exams PM !
1 Login
LOG IN WITH
OR SIGN UP WITH DISQUS ?
Name
ALSO ON EXAMS PM
Quality Management: PMP Study Guide (PMBOK 6th How to Memorize the PMP Process Chart in the
Edition) PMBOK Guide
1 comment • a year ago 1 comment • a year ago
Adrian M — There is no rule of seven, or process Holger Hoppe — Hi, very nice approach to get the table into
improvement plan, mentioned in PMBOK 6th edition. the brain! Thanks. But did you do yourself this way? Tasks are
mentioned twice (perform Integrated Chane Control, …
How many PMBOK knowledge areas are there in the Cost Management: PMP Study Guide (PMBOK 6th
6th Edition? Edition)
1 comment • a year ago 1 comment • a year ago
Waqas Nasir — This information is out dated .. You just Oded — The interpretation for VAC is wrong. VAC > 0 is under
changed the title to PMBOK 6th Edition , rest is old .. The budget, VAC < 0 is over budget.
process model is changed, There are more processes now. …