Page 108 -

6 - PROJECT TIME MANAGEMENT

6.3.1.2 Activity List

See Section 6.3.1.2 of the PMBOK Guide.
®

6.3.1.3 Activity Attributes

See Section 6.3.1.3 of the PMBOK Guide.
®

6.3.1.4 Milestone List

See Section 6.3.1.4 of the PMBOK Guide.
®

6.3.1.5 Project Scope Statement

See Section 6.3.1.5 of the PMBOK Guide.
®

6.3.1.6 Enterprise Environmental Factors

See Section 6.3.1.6 of the PMBOK Guide.
®

6.3.1.7 Organizational Process Assets

See also Section 6.3.1.7 of the PMBOK Guide. Governance models often have milestones, templates, and
®
environmental factors that can provide inputs to sequencing activities for software projects. The enterprise
architecture, when applicable, may also impact sequencing. Organizational parameters for valuing software
investments may be of use in identifying the value of functionality to be provided and thus impact sequencing.

6.3.1.8 Architectural and IV&V Constraints

Architectural constraints (e.g., what needs to be built first) and independent verification and validation (IV&V)
planning may provide inputs that will impact sequencing. In the latter case (IV&V) there may be scheduling
constraints for product features needed to verify and validate cross functional, multi-system, multi-platform, or
multi-environment requirements.

6.3.1.9 Safety and Security Analyses

Safety and cyber security issues may impact the sequencing of some software activities to meet requirements,
policies, and standards. Certification activities are expensive, so certification requirements as inputs to schedule
sequencing should try to minimize the number of certification cycles in the schedule.

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