Page 198 -
P. 198
10 - PROJECT COMMUNICATIONS MANAGEMENT
10.3.3.3 Project Management Plan Updates
See Section 10.3.3.3 of the PMBOK Guide.
®
10.3.3.4 Project Documents Updates
See Section 10.3.3.4 of the PMBOK Guide.
®
10.3.3.5 Organizational Process Assets Updates
See Section 10.3.3.5 of the PMBOK Guide.
®
10.3.3.6 Iteration and Release Plan Updates
An iteration plan confirms the project team’s commitment to the work to be done and the software to be delivered
at the end of the next iteration. A release plan describes when demonstrable, working software will be available
(for demonstration or for release into the users’ environment) and what features and functionality will be included.
For adaptive life cycle software projects, it is important to distribute and explain updates to iteration and release
plans because they may change frequently.
10.3.3.7 Reprioritized Backlog
When using adaptive life cycles for software projects, the customer has the opportunity to reprioritize the
backlog of features to be developed throughout the project life cycle. The backlog of features to be developed
implies the remaining work to be done and the current priorities. The backlog also shows the planned sequence
of development and the schedule forecast, which can be developed using velocity averaged over recent iterative
development cycles. The backlog of product features and remaining work, along with estimates of scheduled
feature delivery, are important elements of project communication that help to control customer/user/product
owner expectations and eliminate unpleasant surprises.
190 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®
