Page 120 -

6 - PROJECT TIME MANAGEMENT

6.6.2 Develop Schedule: Tools and Techniques

The tools and techniques for developing a project schedule in Section 6.6.2 of the PMBOK Guide are applicable
®
for developing a software project schedule, with the modification of Section 6.6.2.8. In addition, the extensions
described in Sections 6.6.2.7 and 6.6.2.9 (below) are applicable when developing a software project schedule.

6.6.2.1 Schedule Network Analysis

See Section 6.6.2.1 of the PMBOK Guide.
®

6.6.2.2 Critical Path Method

See Section 6.6.2.2 of the PMBOK Guide.
®

6.6.2.3 Critical Chain Method

See Section 6.6.2.3 of the PMBOK Guide.
®

6.6.2.4 Resource Optimization Techniques

®
See Section 6.6.2.4 of the PMBOK Guide.

6.6.2.5 Modeling Techniques

See Section 6.6.2.5 of the PMBOK Guide.
®

6.6.2.6 Leads and Lags

See Section 6.6.2.6 of the PMBOK Guide.
®

6.6.2.7 Schedule Compression

Compressing the schedule of a software project without doing other tradeoffs results in a nonlinear increase
in the number of people needed to meet the schedule because the number of communication paths among more
project members increases exponentially; more effort will be spent on communication and coordination of work
activities. A well-known rule of thumb states that software projects rarely succeed when the project schedule
is compressed more than 25%, regardless of the number of people added to the project because increased
communication and coordination becomes counter-productive. And, the well-known Brooks Law states “adding
manpower to a late project makes it later.” [22]

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