Page 118 -

6 - PROJECT TIME MANAGEMENT

6.5.3.2 Project Documents Updates

See Section 6.5.3.2 of the PMBOK Guide.
®

6.6 Develop Schedule

The form of a software project schedule may be the same as described in Section 6.5 of the PMBOK Guide or
®
it may take a different form altogether. In addition to the approach described in the PMBOK Guide, a more flexible
®
approach facilitates the expected changes that inevitably occur in a software project schedule. Software project
schedules and plans change, driven by customer requests, project feedback, and by the emergence of previously
unidentified work activities. The form of software project schedule used may be unfamiliar to some stakeholders.
For example, a prioritized backlog of work may be the preferred method for illustrating and managing the sequence
of project activities instead of a network diagram. The approach of maintaining a prioritized backlog of work
activities is similar to rolling wave planning, where a top-level schedule is maintained for the entire project and only
the proximate elements of the schedule are completed in detail as the project evolves.

6.6.1 Develop Schedule: Inputs

The inputs for developing a project schedule in the PMBOK Guide are applicable inputs for developing a
®
software project schedule. Additional inputs are described in Section 6.6.1.14.

6.6.1.1 Schedule Management Plan

®
See Section 6.6.1.1 of the PMBOK Guide.

6.6.1.2 Activity List

®
See Section 6.6.1.2 of the PMBOK Guide.

6.6.1.3 Activity Attributes

See Section 6.6.1.3 of the PMBOK Guide.
®

6.6.1.4 Project Schedule Network Diagrams

See Section 6.6.1.4 of the PMBOK Guide.
®

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