Page 105 -
P. 105

6 - PROJECT TIME MANAGEMENT






                   6.2.3 Define Activities: Outputs


                      The outputs in Section 6.2.3 of the PMBOK  Guide are applicable outputs from defining software project activity.
                                                         ®
                   Extension and adaptations are described below.


                   6.2.3.1 Activity List

                      Activity lists for software projects may include coordination with entities external. The software development team
                   may need access to testing facilities and infrastructure equipment, and/or access to multiple user environments.
                   These project elements may be outside the scope of control of the software project manager and may require   6
                   external scheduling to avoid negative impact to the software project schedule. See Section 6.2.3.1 of the PMBOK
                                                                                                                  ®
                   Guide for additional information.


                   6.2.3.2 Activity Attributes

                      See Section 6.2.3.2 of the PMBOK  Guide. In addition, attributes that may be included as outputs from defining
                                                   ®
                   activities in a software project activity list include but are not limited to the following:

                         •  Dependencies and enabling precedent activities,
                         •  Stakeholder value or priority,
                         •  Estimated effort, size, complexity, and/or risk,

                         •  Security and/or safety standards and constraints, and
                         •  Special competencies required of project team members and others.


                   6.2.3.3 Milestone List

                      Milestone lists, as described in Section 6.2.3.3 of the PMBOK  Guide are applicable outputs from defining
                                                                            ®
                   software project activities.

                      Milestones for software projects are defined in various ways for various development environments and project
                   life cycles. For example, some software project life cycles define anchor points, which are points in time when
                   major phase transitions occur in the project life cycle.

                      In predictive software development, milestones may be set to denote requirements and architectural design
                   reviews, customer reviews, and product delivery. Often each milestone includes validation or acceptance criteria,
                   but not always.

                      On-demand scheduling methods do not usually have specified milestones; progress is measured by customer
                   satisfaction within the time-to-complete cadence. Calendar-based coordination conferences may be held to discuss
                   project performance, but these are rarely associated with a specific goal or technical criterion.








                   ©2013 Project Management Institute. Software Extension to the PMBOK  Guide Fifth Edition               95
                                                                   ®
   100   101   102   103   104   105   106   107   108   109   110