Page 124 -

6 - PROJECT TIME MANAGEMENT

time. However, care should be taken when reviewing software performance to ensure that all the ancillary activities
that are not specifically related to the software development are progressing as well. Ancillary activities include
infrastructure support, testing environments, test case development, interface control, configuration management,
equipment or supply acquisition, deployment planning, and logistics activities.

6.7.2.2 Project Management Software

See Section 6.7.2.2 of the PMBOK Guide.
®

6.7.2.3 Resource Optimization Techniques

See Section 6.7.2.3 of the PMBOK Guide.
®

6.7.2.4 Modeling techniques

®
See Section 6.7.2.4 of the PMBOK Guide.

6.7.2.5 Leads and Lags

®
See Section 6.7.2.5 of the PMBOK Guide.

6.7.2.6 Schedule Compression

As described in Section 6.6.2.6 of this Software Extension, schedule compression for software projects results
in a nonlinear increase in the required number of team members. Increased communication and coordination
among more team members and less time to do adequate development and testing may result in decreased
software quality. An alternative to reducing quality is to reduce the number of lower-valued features to be included
in the software product, and/or to reduce the functionality within features to a minimally viable level.

6.7.2.7 Scheduling Tool

See Section 6.7.2.7 of the PMBOK Guide.
®

6.7.2.8 Evidence-Based Reviews

Evidence-based reviews for software projects have been recommended in various standards (including ISO/IEC/
IEEE Standards 1028 and 12207). They include the following guidelines:

• Base reviews on evidence (e.g., demonstration of working software) provided by the developer and
validated by independent experts. A laundry list of work activities completed is not evidence.

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