Plan Sourcing Strategy in PMBOK 8 — Complete Guide

Article updated in March 2026 for the PMBOK® Guide — Eighth Edition.

Plan Sourcing Strategy in PMBOK 8 — Complete Guide

Formerly known as: Plan Procurement Management (PMBOK 6)

It was week three of a $2.4 million ERP implementation when the project manager discovered the catastrophe: three critical software modules had been developed by two separate vendors using incompatible architecture — because nobody had documented a sourcing strategy at the start. Each vendor assumed the other team would handle integration. The client, a regional logistics company, faced an unexpected $180,000 re-architecture bill and a 10-week schedule delay. The executive sponsor called it “the most preventable disaster” she had witnessed in 15 years of project oversight.

Stories like this play out across industries every day. Teams rush into execution, begin soliciting vendors based on habit rather than analysis, and later discover that their sourcing decisions were misaligned with project complexity, risk tolerance, or organizational capacity. The result is cost overruns, vendor disputes, scope gaps, and eroded stakeholder trust — all of which could have been avoided with a disciplined Plan Sourcing Strategy process.

In PMBOK 8, Plan Sourcing Strategy is a formal Governance domain process that requires project teams to make deliberate, documented decisions about whether to use internal or external resources, which selection criteria to apply, and what contract types best serve the project’s risk and value profile. This article gives you the complete picture: definitions, ITTOs from the PDF source, step-by-step application, real-world examples, templates, common errors, and tailoring guidance.

This guide covers:

• What Plan Sourcing Strategy means in PMBOK 8
• How it differs from Plan Procurement Management in PMBOK 6
• Complete ITTOs extracted from the PMBOK 8 PDF
• Step-by-step application for predictive, agile, and hybrid projects
• Two real-world examples (Project Phoenix and ProjectAdm)
• Downloadable templates
• Five common errors and how to avoid them
• Tailoring and process interaction guidance

1. What Is the Plan Sourcing Strategy Process

According to the PMBOK® Guide — Eighth Edition, the Plan Sourcing Strategy process involves documenting project sourcing decisions, specifying the source selection approach, determining the scope of work for external sourcing, and selecting the appropriate contracts and sources for delivering the work. It establishes a clear framework for acquiring project deliverables, either from within the organization or from external sources, defining what to acquire, how to acquire it, and when to acquire it.

The process is used to determine whether work or deliverables can be better accomplished using internal sources or should be purchased from outside sources. This is the foundational make-or-buy analysis that shapes every subsequent procurement decision across the project life cycle.

Plan Sourcing Strategy sits within the Planning phase of the Governance performance domain and is Process 3 of 9 in that domain. It receives inputs from the project charter and project management plan, and its primary output is the sourcing strategy plan — a document that guides all external engagement throughout execution.

PMBOK 6 vs. PMBOK 8 Comparison

A key PMBOK 8 clarification: Plan Sourcing Strategy differs from the Plan Resource Management process (covered in the Resources performance domain) in that it specifically deals with outsourcing project work and deliverables, taking into account scope, time, cost, quality, and resource requirements from outside the organization.

2. Why Use the Plan Sourcing Strategy Process

Without a documented sourcing strategy, project teams default to informal habits — calling the same vendor they used last time, assuming the procurement team will “figure it out,” or splitting work between internal and external teams with no integration plan. The consequences are predictable and expensive.

Direct Benefits

• Clarity on what to acquire and from whom: The process forces explicit decisions about every major deliverable, so there are no gaps or unexpected dependencies at execution time.
• Risk transfer to appropriate parties: One of the chief advantages of outsourcing, per PMBOK 8, is that it transfers delivery risk to the supplier when the goods or services are common and the supplier has greater competence.
• Freeing internal capacity for competitive strengths: When the organization’s core value lies in a specific capability, outsourcing commodity work frees resources to focus on those competitive strengths.
• Transparent vendor selection: Documented source selection criteria ensure consistency and fairness in vendor evaluation, reducing legal and compliance exposure.
• Aligned contract types: Different project contexts demand different contract structures; the sourcing strategy plan ensures contract types match the project’s risk profile.
• Stronger stakeholder confidence: An explicit sourcing strategy demonstrates governance maturity and reduces sponsor anxiety about external dependencies.

Cost of Skipping This Process

• Uncontrolled vendor proliferation — multiple vendors engaged without coordination
• Misaligned contract types that expose the organization to cost overruns or liability
• Missed insourcing opportunities where internal expertise could have delivered higher quality at lower cost
• Source selection inconsistency leading to disputes, grievances, or audit findings
• Integration failures when vendors work from incompatible assumptions

3. Inputs, Tools & Techniques, and Outputs (ITTO)

The following ITTO table is extracted directly from the PMBOK® Guide — Eighth Edition, Figure 2-5 (page 125 of the source PDF).

Key ITTO Explanations

Inputs

• Project charter: Establishes the overall project authorization, objectives, and constraints that define the boundaries within which sourcing decisions must fit. The charter’s budget and timeline parameters shape the feasibility of external sourcing.
• Project management plan components: The scope management plan defines what work needs to be done (and therefore what might be outsourced). The quality management plan sets quality thresholds that vendors must meet. The schedule management plan indicates timing constraints for vendor deliveries. The financial management plan governs payment structures and budget authority.
• Requirements documentation & traceability matrix: These documents specify exactly what deliverables must satisfy; they form the basis for statements of work and vendor evaluation criteria.
• Risk register: Informs make-or-buy decisions by identifying which work packages carry risk best transferred to an external specialist versus risk best retained internally.
• Stakeholder register: Identifies procurement stakeholders including legal counsel, finance, procurement department, and end users whose requirements must be reflected in sourcing decisions.
• Enterprise environmental factors: Include market conditions, regulatory requirements, legal constraints, and organizational procurement policies that constrain or enable sourcing options.

Tools & Techniques

• Expert judgment: Leverages procurement specialists, legal counsel, finance analysts, and subject matter experts to evaluate feasibility, risk, and value of different sourcing approaches.
• Market research: Examines vendor market conditions — availability, capacity, pricing benchmarks, and emerging capabilities — to inform realistic sourcing decisions. PMBOK 8 emphasizes that market research grounds sourcing decisions in current market reality rather than historical assumptions.
• Make-or-buy analysis: The structured comparison of internal versus external delivery options. PMBOK 8 identifies specific advantages of each (see table below). The analysis considers cost, capability, strategic alignment, risk, and capacity.
• Source selection analysis: Evaluates potential vendors or internal teams against defined criteria to identify the best source for each work package.
• Document analysis: Reviews existing contracts, past vendor performance data, lessons learned registers, and organizational procurement templates to inform strategy development.

Make-or-Buy Decision Factors (from PMBOK 8, Table 2-3)

Outputs

• Sourcing strategy plan: The primary output. This document records all make-or-buy decisions, defines source selection criteria, identifies the contract types for each external engagement, and establishes the process for managing external source relationships. It includes risk mitigation approaches for vendor-related risks and communication protocols for the project life cycle. Participants documented in the plan may include the purchasing or procurement department and personnel from the buying organization’s legal department.

4. Step-by-Step Application Guide

1. Assemble the sourcing team. Convene key participants early — project manager, procurement lead, legal counsel, finance representative, and relevant technical subject matter experts. The PMBOK 8 notes that participants may include the purchasing or procurement department as well as personnel from the legal department. Assign roles and document responsibilities in the sourcing strategy plan from the start.
2. Identify all work packages requiring a sourcing decision. Review the scope baseline (WBS) and requirements documentation to create a comprehensive list of deliverables that need to be produced. For each deliverable or work package, flag whether internal capacity exists and whether the work requires specialized external expertise. Do not assume everything is done internally by default.
3. Conduct make-or-buy analysis for each candidate work package. Apply the PMBOK 8 make-or-buy framework systematically. Consider availability of internal expertise, strategic alignment, cost comparison, risk profile, and capacity constraints. Document the rationale for each decision in the sourcing strategy plan so that decisions are traceable and defensible.
4. Perform market research for externally sourced items. For all work packages earmarked for outsourcing, conduct market research to assess vendor availability, pricing benchmarks, lead times, and capability levels. This is especially important for specialized or emerging technologies where vendor capacity may be limited.
5. Define source selection criteria. Establish clear, weighted criteria for each externally sourced item. Per PMBOK 8, criteria may include cost, technical capability, past performance, financial stability, compliance with requirements, and alignment with organizational values or sustainability goals. Clearly defined criteria ensure transparency and consistency in vendor selection.
6. Select appropriate contract types. Determine what type of contract (e.g., fixed-price, cost-reimbursable, time-and-materials) best aligns with the project’s risk profile, the vendor’s delivery certainty, and the organization’s governance requirements. Fixed-price contracts transfer risk to vendors for well-defined scope; cost-reimbursable contracts are better for uncertain or innovative work.
7. Document and communicate the sourcing strategy plan. Consolidate all decisions into the sourcing strategy plan, including insourcing/outsourcing decisions, source selection criteria, contract type selections, relationship management processes, and risk mitigation approaches. Share the plan with all relevant stakeholders — procurement, legal, finance, project team — and integrate it into the overall project management plan.

5. When to Apply This Process

The Plan Sourcing Strategy process applies to projects where there is a need to use external sources to complete project work. It is conducted during the planning phase and should be completed before any vendor solicitation or engagement begins. Key triggers include:

• The project scope includes deliverables requiring specialized external expertise not available internally
• Internal capacity is constrained and external augmentation is needed
• The organization’s risk policy requires cost or delivery risk to be transferred to suppliers
• Regulatory requirements mandate the use of pre-qualified external vendors
• Strategic priorities suggest internal teams should focus on core capabilities rather than commodity work

Predictive vs. Agile Contexts

In predictive projects, the Plan Sourcing Strategy process is typically conducted once during initial planning, producing a comprehensive sourcing strategy plan that governs the entire project. All make-or-buy decisions are documented upfront and change-controlled thereafter.

In agile and adaptive projects, sourcing decisions may be revisited at the beginning of each iteration or release cycle as the backlog evolves. The sourcing strategy plan may be a lighter document — perhaps a sourcing decision log or procurement canvas — that is updated incrementally as requirements become clearer.

In hybrid projects, the initial high-level sourcing strategy is established in the planning phase, but detailed vendor selection for specific work packages may be deferred and executed in an adaptive manner as scope is progressively elaborated.

6. Real-World Examples

Example 1: Project Phoenix — Website Launch

TechCorp, a mid-sized technology firm, launched Project Phoenix — a complete rebuild of their customer portal with a $72,250 budget and a 90-day deadline. Sarah Chen, the CEO, appointed Alex Morgan, PMP, as project manager. The team needed to plan sourcing strategy PMBOK 8-style from day one.

Alex convened the sourcing team — including TechCorp’s in-house development lead, the procurement coordinator, and external legal counsel — in week one. Together they mapped the WBS and identified four major work packages: UX design, front-end development, back-end API integration, and security testing.

The make-or-buy analysis revealed a decisive split: front-end development and back-end integration were strong candidates for insourcing (TechCorp had experienced developers and the work was strategically core), while UX design was outsourced to a specialized agency (internal capacity was insufficient) and security testing was contracted to a third-party auditor (required certification that could not be obtained internally within the timeline).

Alex defined source selection criteria for both outsourced work packages. For UX design: portfolio quality (40%), methodology fit (30%), timeline reliability (20%), and cost (10%). For security testing: certification status (50%), past performance on similar platforms (30%), and response time commitment (20%).

The sourcing strategy plan documented fixed-price contracts for both external engagements (scope was well-defined) and established weekly check-in protocols with each vendor. When the UX agency delivered initial wireframes two days late in week four, the contract’s late-delivery clause triggered a remediation process that kept the project on track. Sarah Chen later credited the sourcing strategy as the “invisible backbone” of Project Phoenix’s on-time, on-budget delivery.

Example 2: Project ProjectAdm — SaaS PM Platform

Eduardo, project manager at a mid-size software firm, was tasked with building ProjectAdm — a SaaS project management platform designed to compete in the SME market. The team was 12 people with diverse skills but limited expertise in certain cloud infrastructure components and data analytics.

During the plan sourcing strategy PMBOK 8 process, Eduardo led a market research exercise that surfaced a critical insight: cloud infrastructure setup and database optimization could be completed faster and cheaper by a specialist vendor than by developing internal capability — consistent with the PMBOK 8 principle that outsourcing is often less expensive when the goods or services are common.

Eduardo’s make-or-buy analysis documented that the core platform product logic (user stories, workflow engine, API design) would be insourced to maintain proprietary advantage. Cloud DevOps setup, database optimization, and penetration testing would be outsourced. Source selection criteria for DevOps included AWS/Azure certification, proven SaaS deployment track record, and CI/CD pipeline expertise.

The plan also chose a time-and-materials contract for the DevOps vendor due to scope uncertainty in the early infrastructure design phase, with a transition to a fixed-price ongoing support contract once the infrastructure was stable. This contract type selection proved critical: the initial T&M engagement allowed scope to evolve over six weeks without disputes, and the subsequent fixed-price support contract provided budget predictability for the remaining 18 months.

Eduardo’s team successfully launched ProjectAdm on schedule. The plan sourcing strategy PMBOK 8 approach — documented, deliberate, and integrated with the project management plan — prevented two potential vendor conflicts and a scope gap that manual approaches would have missed.

7. Templates and Downloads

Apply what you learned with these ready-to-use templates from projectmanagement.com.br:

• Sourcing Strategy Plan Template — Complete sourcing strategy plan with make-or-buy analysis section, source selection criteria matrix, and contract type decision guide
• Project Management Plan Template — Full PMP template including the procurement/sourcing component

8. Five Common Errors

1. Error: Skipping market research and relying on known vendors.
   Teams default to familiar vendors without assessing whether better options exist. This leads to paying above-market rates or missing superior capability.
   How to avoid: Treat market research as a mandatory step, even for smaller contracts. Allocate specific time in the planning schedule for research and document findings in the sourcing strategy plan.
2. Error: Treating all work packages the same in the make-or-buy analysis.
   Project managers apply a blanket “outsource everything” or “insource everything” policy without evaluating each work package on its own merits. This misallocates resources and creates unnecessary risk.
   How to avoid: Conduct a structured make-or-buy analysis for every significant work package using the PMBOK 8 framework. Document the specific rationale for each decision.
3. Error: Failing to define source selection criteria before solicitation.
   Teams engage vendors informally, then struggle to compare proposals objectively. Undocumented selection often leads to bias, disputes, or regulatory violations.
   How to avoid: Define, weight, and document source selection criteria — including cost, technical capability, past performance, financial stability, compliance, and values alignment — before issuing any request for proposal.
4. Error: Selecting the wrong contract type.
   Using fixed-price contracts for poorly defined scope forces vendors to either over-price or under-deliver. Using time-and-materials contracts for well-defined work removes cost accountability.
   How to avoid: Match contract type to scope certainty. Use PMBOK 8 guidance: fixed-price for clear scope, cost-reimbursable for uncertain or innovative work, time-and-materials for small or exploratory engagements.
5. Error: Treating the sourcing strategy plan as a one-time planning artifact.
   Plans are created and then ignored during execution. Vendor relationships evolve, risks materialize, and scope changes — yet the sourcing strategy is never updated.
   How to avoid: Establish a cadence for reviewing and updating the sourcing strategy plan. Per PMBOK 8, the Plan Sourcing Strategy process links to Monitor and Control Project Performance — update the sourcing strategy when conditions change.

9. Tailoring This Process

Additional tailoring considerations from PMBOK 8 include the regulatory environment (heavily regulated industries require more formal sourcing governance), the organizational governance framework (large organizations with PMOs and dedicated procurement departments require tighter integration), and the sustainability or values-based criteria that increasingly feature in vendor selection.

10. Process Interactions

The Plan Sourcing Strategy process is deeply interconnected within the PMBOK 8 Governance domain and with other performance domains:

• Feeds into this process:
  • Initiate Project or Phase — the project charter provides authorization boundaries and budget constraints that shape sourcing decisions
  • Integrate and Align Project Plans — the project management plan components (scope baseline, resource management plan, financial plan) are primary inputs
• This process feeds into:
  • Execute Sourcing Strategy (Process 4) — the sourcing strategy plan directly governs how vendors are engaged and managed during execution
  • Control Project Performance (Process 7) — vendor performance metrics and contract compliance become monitoring inputs
  • Manage Change (Process 8) — changes to scope or vendor performance trigger updates to the sourcing strategy plan
  • Close Project or Phase (Process 9) — contract closure procedures and vendor performance records must be handled during project closure
• External interactions:
  • Resources performance domain — Plan Sourcing Strategy is explicitly distinguished from Plan Resource Management (resources domain), which covers internal resource planning
  • Risk performance domain — the risk register informs sourcing decisions, and sourcing decisions create new risks that feed back into the risk register
  • Finance performance domain — contract types and payment terms directly affect project cash flow and financial forecasts

For the full Governance domain process map, see our PMBOK 8 Complete Index.

11. Quick-Application Checklist

• Assembled sourcing team including procurement, legal, and finance representatives
• Reviewed WBS and requirements documentation to identify all work packages requiring sourcing decisions
• Completed formal make-or-buy analysis for every significant work package
• Conducted market research for all work packages earmarked for outsourcing
• Defined and weighted source selection criteria for each external engagement
• Selected appropriate contract type for each external work package
• Documented insourcing/outsourcing decisions with rationale in the sourcing strategy plan
• Established vendor relationship management and communication protocols
• Identified vendor-related risks and documented mitigation approaches
• Integrated sourcing strategy plan into the overall project management plan
• Communicated sourcing strategy to all relevant stakeholders
• Established a review cadence to update the sourcing strategy as the project evolves

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.