Page 190 -
P. 190
10 - PROJECT COMMUNICATIONS MANAGEMENT
10.2 Manage Communications
The inputs, tools and techniques, and outputs in Section 10.2 of the PMBOK Guide are applicable to managing
®
software project communications.
10.2.1 Manage Communications: Inputs
The inputs in Section 10.2.1 of the PMBOK Guide are applicable inputs for managing software project
®
communications. In addition, the input in Section 10.2.1.5 of this Software Extension applies to managing software
project communications.
10.2.1.1 Communications Management Plan
See Section 10.2.1.1 of the PMBOK Guide.
®
10.2.1.2 Work Performance Reports
See Section 10.2.1.2 of the PMBOK Guide.
®
10.2.1.3 Enterprise Environmental Factors
See Section 10.2.1.3 of the PMBOK Guide.
®
10.2.1.4 Organizational Process Assets
See Section 10.2.1.4 of the PMBOK Guide.
®
10.2.1.5 Release and Iteration Plans
As stated in Section 10.1.1 of this Software Extension, adaptive life cycles for software projects typically include
iteration and release plans. These plans provide an important input for managing software project communications.
10.2.2 Manage Communications: Tools and Techniques
The tools and techniques in Section 10.2.2 of the PMBOK Guide are applicable tools and techniques for
®
managing software project communications. In addition, Sections 10.2.2.6 to 10.2.2.9 provide extensions that are
applicable to managing software project communications.
Because of the potential for high rates of change and the lack of a tangible, evolving product, tools and techniques
for managing communications on software projects are especially important. Project information can be provided
by means of push and pull mechanisms. Information such as status reports should be pushed out to stakeholders
on a regular basis (perhaps weekly). Information can be published in a repository so that stakeholders can pull the
desired information at the desired level of detail, as needed or desired.
182 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®
