Page 195 -

10 - PROJECT COMMUNICATIONS MANAGEMENT

For predictive software project life cycles, the following measures can be used: milestones achieved and missed,
status of change requests and the risk register, status of software construction and testing, status of increments
planned and developed, and issues identified and resolved by software quality assurance and software quality
control personnel. 10

For adaptive software project life cycles, the content of the evolving software product is the primary measure of
progress. Iterations of the life cycle add increments to the evolving product. Newly added content, in combination
with existing content, is tested and demonstrated at the end of the iterations. The demonstrations, in combination
with the prioritized features in the product backlog (prioritized by business value), provide a measure of value-
adding work that remains to be done. For adaptive life cycles, metrics such as stories developed (and tested)
compared to stories remaining, meet the criteria of being simple to produce and relevant to the end goal.

Adaptive reporting tools such as cumulative flow diagrams, burnup/burndown graphs, and parking lot diagrams
also provide valuable project information.

10.3.1 Control Communications: Inputs

The inputs in Section 10.3.1 of the PMBOK Guide are applicable inputs for controlling software project
®
communications. In addition, the inputs in 10.3.1.6 and 10.3.1.7 of this Software Extension are applicable for
controlling software project communications.

10.3.1.1 Project Management Plan

See Section 10.3.1.1 of the PMBOK Guide.
®

10.3.1.2 Project Communications

See Section 10.3.1.2 of the PMBOK Guide.
®

10.3.1.3 Issue Log

See Section 10.3.1.3 of the PMBOK Guide.
®

10.3.1.4 Work Performance Data

See Section 10.3.1.4 of the PMBOK Guide.
®

10.3.1.5 Organizational Process Assets

See Section 10.3.1.5 of the PMBOK Guide.
®

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