Page 228 -

12 - PROJECT PROCUREMENT MANAGEMENT

Outputs from planning software procurement management include: (a) a list of potential suppliers, (b) technical and
managerial requirements, (c) a statement of objectives or statement of work, (d) evaluation criteria, (e) preferred
terms and conditions, and (f) a request for proposals or request for tender.

A request for proposal (RFP) provides the necessary information to potential suppliers. It includes the technical
requirements (SOO or SOW), the terms and conditions, the evaluation criteria for the proposal and the delivered
software product, and instructions for bidders. The instructions explain what information should be included in
the proposal, the anticipated procurement schedule, and the anticipated start date and period of performance.
Instructions often specify a maximum length for the proposal and the required structure of the proposal, so
responses can be more easily compared. Software proposal instructions commonly require that proposals contain
information needed to evaluate a bidder’s capabilities and stability, such as descriptions of related projects,
customer references, information on the qualifications of key personnel and staff certifications, and descriptions
of facilities and technical resources.

12.1.3.1 Procurement Management Plan

See Section 12.1.3.1 of the PMBOK Guide.
®
12
12.1.3.2 Procurement Statement of Work

See Section 12.1.3.2 of the PMBOK Guide.
®

12.1.3.3 Procurement Documents

See Section 12.1.3.3 of the PMBOK Guide.
®

12.1.3.4 Source Selection Criteria

See Section 12.1.3.4 of the PMBOK Guide.
®

12.1.3.5 Make-or-Buy Decisions

See Section 12.1.3.5 of the PMBOK Guide.
®

12.1.3.6 Change Requests

See Section 12.1.3.6 of the PMBOK Guide.
®

12.1.3.7 Project Documents Updates

®
See Section 12.1.3.7 of the PMBOK Guide.

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