Page 67 -

4 - PROJECT INTEGRATION MANAGEMENT

4.3.3 Direct and Manage Project Work: Outputs

The outputs presented in Section 4.3.3 of the PMBOK Guide are applicable for directing and managing software
®
project execution. Additional outputs are provided in Sections 4.3.3.2 and 4.3.3.6 of this Software Extension.

4.3.3.1 Deliverables
4
See Section 4.3.3.1 of the PMBOK Guide.
®

4.3.3.2 Work Performance Data

See Section 4.3.3.2 of the PMBOK Guide.
®

Productivity and progress indicators such as velocity and burndown and burnup charts provide work performance
data for adaptive life cycle software projects (see the Glossary for definitions of these terms).

4.3.3.3 Change Requests

See Section 4.3.3.3 of the PMBOK Guide.
®

4.3.3.4 Project Management Plan Updates

See Section 4.3.3.4 of the PMBOK Guide.
®

4.3.3.5 Project Documents Updates

See Section 4.3.3.5 of the PMBOK Guide.
®

4.3.3.6 Demonstrations of Working, Deliverable Software

In addition to the outputs contained in Section 4.3.3 of the PMBOK Guide, frequent and ongoing demonstrations
®
of working, deliverable software are the most important indicators of tangible progress for software projects.

4.4 Monitor and Control Project Work

The inputs, tools and techniques, and outputs for monitoring and controlling project work in Section 4.4 of
®
the PMBOK Guide are applicable for monitoring and controlling software project work. In addition, increments of
working software code can be evaluated against the project and product constraints, the team performance, and
the overall goals of the project to trigger change control events, as necessary, when those events exceed control
limits. A scope management plan, perhaps including a prioritization scheme and business rules, can be helpful in
managing scope changes that fall outside of the control limits of the project or product.

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