Page 72 -
P. 72

4 - PROJECT INTEGRATION MANAGEMENT






                   4.5.3.4 Project Documents Updates


                      See Section 4.5.3.4 of the PMBOK  Guide.
                                                   ®

                   4.6 Close Project or Phase


                      According to Section 4.6 of the PMBOK  Guide, Close Project or Phase is the process of finalizing all activities
                                                       ®
                   across all five Project Management Process Groups to formally complete the project or phase. The inputs, tools
                   and techniques, and outputs for closing a project in Section 4.6 of the PMBOK  Guide are applicable to closing a
                                                                                      ®
                   software project, project phase, or iteration cycle.

                      Two items are particularly important when closing a software project: historical productivity data and lessons
                   learned. This information should be captured in organizational data repositories. Historical data provides a basis
                   for estimating future, similar projects. Historical data and lessons learned can be used to identify trends, both
                   positive and negative, during the life cycle of a project. Positive trends can indicate areas for organizational process
                   improvement by indicating good practices used on the project that should be adopted throughout the organization.
                   Negative trends and lessons learned indicate areas for needed process improvements throughout the software
                   organization. Adherence to requirements for legal review and approval may be an important additional element of
                   the closing process for software projects.

                      For purposes of future sustainment and possible reuse of the software, the software project manager, and others,
                   as appropriate, should arrange for continuing configuration control of the software assets, such as requirements,
                   source code, and associated architecture and design documentation for the life of the software product.



                   4.6.1 Close Project or Phase: Inputs


                      The inputs for closing a project or phase in Section 4.6.1 of the PMBOK  Guide are applicable inputs for closing
                                                                                 ®
                   a software project, phase, or iteration cycle.


                   4.6.1.1 Project Management Plan

                      See Section 4.6.1.1 of the PMBOK  Guide.
                                                   ®

                   4.6.1.2 Accepted Deliverables

                      See Section 4.6.1.2 of the PMBOK  Guide.
                                                   ®


                   4.6.1.3 Organizational Process Assets

                      See Section 4.6.1.3 of the PMBOK  Guide.
                                                   ®





          60       ©2013 Project Management Institute. Software Extension to the PMBOK  Guide Fifth Edition
                                                                   ®
   67   68   69   70   71   72   73   74   75   76   77