Page 109 -
P. 109

6 - PROJECT TIME MANAGEMENT






                   6.3.2 Sequence Activities: Tools and Techniques


                      The tools and techniques for sequencing project activities in Section 6.3.2 of the PMBOK  Guide are applicable
                                                                                                ®
                   for sequencing software project activities. In addition to these, the tools and techniques in 6.3.2.5 through 6.3.2.8
                   of this Software Extension are applicable for sequencing software project activities.


                   6.3.2.1 Precedence Diagramming Method (PDM)

                      See Section 6.3.2.1 of the PMBOK  Guide.
                                                   ®
                                                                                                                          6
                   6.3.2.2 Dependency Determination

                      See Section 6.3.2.2 of the PMBOK  Guide.
                                                   ®

                   6.3.2.3 Leads and Lags


                      See Section 6.3.2.3 of the PMBOK  Guide.
                                                   ®

                   6.3.2.4 SAIV and Time Boxing

                      Using SAIV (schedule as independent variable) for sequencing software project activities can help to ensure
                   that the most valuable features or functionality are available when time is exhausted, provided the most important
                   features have been implemented first. The SAIV concept is applied in a variety of situations, including time boxing
                   and date-certain scheduling. As shown in Figure 6-3, product scope can be determined when cost and time have
                   been set. SAIV can be applied to software increments, intermediate releases, or completed products.

                      This method depends on the ability to prioritize items of work for valued-added requirements, stories, or features.
                   The value-added may change over time, but adaptive life cycles allow for that change by frequently reassessing
                   value. This assumes that the customer or other stakeholders are either available or are represented by surrogates
                   whenever values are reassessed.


                   6.3.2.5 Work in Progress Limits and Classes of Service


                      See on-demand scheduling in Section 6.1 of this Software Extension.


                   6.3.2.6 Feature Set Evaluation

                      A feature set includes a collection of features that deliver business value; feature sets are often derived from
                   user stories. Figure 6-4 illustrates construction and evaluation of software for the features in an iteration feature set.
                   Activities needed to implement features are usually sequenced one feature at a time. Evaluation of an implemented
                   feature may affect sequencing of other features or feature sets.





                   ©2013 Project Management Institute. Software Extension to the PMBOK  Guide Fifth Edition               99
                                                                   ®
   104   105   106   107   108   109   110   111   112   113   114