Page 234 -

12 - PROJECT PROCUREMENT MANAGEMENT

12.3.3.4 Project Documents Updates

See Section 12.3.3.4 of the PMBOK Guide.
®

12.3.3.5 Organizational Process Assets Updates

See Section 12.3.3.5 of the PMBOK Guide.
®

12.4 Close Procurements

The considerations for closing software procurements in Section 12.4 of the PMBOK Guide are applicable for
®
closing software procurements, with the following extensions.

While a software procurement activity usually ends before the software project ends, the need for the acquired
service or software product may continue. Closing one procurement activity may signal the need to open another
for ongoing maintenance. Another consideration is long-term relevance of the technology and the ability of the
supplier to support technical change over time. When a software project manager plans to integrate a COTS
product or custom-built software into their product, the project manager needs to be aware that the technology
used to develop the COTS product or custom-built software could adversely affect the ability to make product 12
enhancements in the future.

12.4.1 Close Procurements: Inputs

The inputs in Section 12.4.1 of the PMBOK Guide are applicable inputs for closing software procurements.
®

12.4.1.1 Project Management Plan

See Section 12.4.1.1 of the PMBOK Guide
®

12.4.1.2 Procurement Documents

®
See Section 12.4.1.2 of the PMBOK Guide

12.4.2 Close Procurements: Tools and Techniques

The tools and techniques in Section 12.4.2 of the PMBOK Guide are applicable for closing software procurements.
®

12.4.2.1 Procurement Audits

See Section 12.4.2.1 of the PMBOK Guide.
®

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