Page 186 -

10 - PROJECT COMMUNICATIONS MANAGEMENT

Project Communications
Management Overview

10.1 Plan Communications 10.2 Manage 10.3 Control
Management Communications Communications
.1 Inputs .1 Inputs .1 Inputs
.1 Project management plan .1 Communications management .1 Project management plan
.2 Stakeholder register plan .2 Project communications
.3 Enterprise environmental .2 Work performance reports .3 Issue log
factors .3 Enterprise environmental .4 Work performance data
.4 Organizational process assets factors .5 Organizational process assets
.4 Organizational process assets .6 Prioritized backlog
.2 Tools & Techniques .5 Release and iteration plans .7 Velocity statistics and
.1 Communication requirements projections
analysis .2 Tools & Techniques
.2 Communication technology .1 Communication technology .2 Tools & Techniques
.3 Communication models .2 Communication models .1 Information management
.4 Communication methods .3 Communication methods systems
.5 Meetings .4 Information management .2 Expert judgment
systems .3 Meetings
.3 Outputs .5 Performance reporting .4 Considerate communications
.1 Communications management .6 Information radiators .5 Automated systems
plan .7 Velocity
.2 Project documents updates .8 Historical velocity .3 Outputs
.9 Online collaboration tools .1 Work performance information
.2 Change requests
.3 Outputs .3 Project management plan
.1 Project communications updates
.2 Project management plan .4 Project documents updates
updates .5 Organizational process assets
.3 Project documents updates updates
.4 Organizational process assets .6 Iteration and release plan
updates updates
.5 Special communication tools .7 Reprioritized backlog
.6 Online collaboration tools
.7 Updated information radiators

Figure 10-1 Project Communications Management Overview

Face-to-face (FTF) communication allows two-way dialogs; issues and questions can be addressed immediately,
and emotion is readily conveyed. For example, while discussing a topic, when a person nods their head or otherwise
indicates understanding or agreement with the speaker, further explanation can be curtailed, and the discussion
can be directed to other topics. Because of the higher bandwidth, opportunities for questions and answers, and
lower communication costs, face-to-face communication is the preferred means of communication for software
development projects, whenever possible. It is easy to productively use face-to-face communication for colocated
teams. Audio and video conferencing can be used to simulate face-to-face interactions when team members are
geographically distributed.
To facilitate communication, the preferred solution for a large project is to break up a large team into multiple
smaller teams that can leverage face-to-face communication and tacit knowledge within each of the smaller
teams, and with well-defined communication channels among the teams.

178 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®