Page 111 -

6 - PROJECT TIME MANAGEMENT

6.3.2.7 Service-Level Agreements

There may be a service-level agreement between a project manager and a customer (or other stakeholder)
that specifies the amount of work to be accomplished over a specified period of time. This establishes the project
capacity and may impact sequencing of activities.

6.3.3 Sequence Activities: Outputs

The outputs from sequencing activities in the PMBOK Guide are applicable as outputs from sequencing
®
software project activities. In addition, the outputs specific to software project sequencing activities are described 6
in Sections 6.3.3.3, 6.3.3.4, and 6.3.3.5 of this Software Extension.

6.3.3.1 Project Schedule Network Diagrams

See Section 6.3.3.1 of the PMBOK Guide.
®

6.3.3.2 Project Documents Updates

See Section 6.3.3.2 of the PMBOK Guide.
®

6.3.3.3 Features Sets

A feature set includes a collection of features that deliver business value; feature sets are often derived from
user stories.

6.3.3.4 Release Plans

A release plan specifies the overall project schedule of releases for delivery of software capabilities; it may
be one of the outputs of sequencing activities for software projects. Release delivery may be for customer/user
evaluation or for delivery into the users’ environment. The release plan is highly dependent upon the production
rate of the software team. Comparing estimated time to the actual time taken to accomplish work over a period of
several iterative development cycles provides a baseline for estimating the time for future releases.

6.3.3.5 Architectural and Nonfunctional Dependencies

The outputs of sequencing software project activities may be influenced by architectural and nonfunctional
dependencies intended to avoid duplication of work or rework by other project teams or initiatives. In turn, these
dependencies may need to be updated based on the scheduled project activities.

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