PMBOK 8 Make-or-Buy, Sourcing, and Vendor Fit in Project Decisions

Study PMBOK 8 Make-or-Buy, Sourcing, and Vendor Fit in Project Decisions: key concepts, common traps, and exam decision cues.

Make-or-buy analysis is really a control-and-capability decision before it is a pricing decision. PMBOK 8 presents procurement as part of project success, not as a detached purchasing step. The project manager needs to ask what should stay close to the team, what can be sourced externally, and what the sourcing choice does to risk, coordination, and delivery speed.

Why This Matters For PMP 2026

Procurement questions are often disguised value and risk questions. The weaker answer chases the cheapest option or assumes that outsourcing always increases efficiency. The stronger answer looks at fit:

  • does the team already have the capability
  • does the work require close control or sensitive coordination
  • does external sourcing create integration or dependency risk
  • does the decision improve or weaken value delivery

A Make-Or-Buy Matrix

Decision factor More likely to keep in-house More likely to source externally
Strategic sensitivity High Lower
Internal capability Strong and available Weak, scarce, or unavailable
Need for tight coordination High Moderate or manageable through interfaces
Speed advantage Internal team can move faster Market can deliver faster
Specialized expertise Already present Better available externally
Confidentiality concern High Lower or contractually manageable

This matrix is not a formula. It is a way to see that make-or-buy is about fit, not habit.

What Sourcing Strategy Is Really Solving

Sourcing strategy answers questions such as:

  • what work the project should control directly
  • what work can be obtained more effectively outside
  • how much uncertainty exists in the deliverable
  • how supplier coordination will affect schedule and quality
  • what commercial and governance risks the project can absorb

That means a sourcing decision changes more than vendor ownership. It can reshape dependency management, communication load, contract monitoring, and stakeholder expectations.

Why Vendor Fit Matters More Than Lowest Price

Once external sourcing is justified, the project still has to choose the right vendor. Vendor fit includes:

  • capability in the specific work
  • credible references and delivery history
  • ability to meet timing and integration needs
  • willingness to work within the needed governance model
  • maturity in communication, issue handling, and change discipline

Lowest price can matter, but it is often a weak primary lens when uncertainty, complex integration, or rework risk is high.

Common Trap Patterns

The first trap is cheapest-is-best thinking: choosing the lowest price without accounting for risk, coordination, and control cost.

The second trap is outsource-by-default logic: assuming external sourcing is automatically faster or better.

The third trap is fit blindness: evaluating vendors on price and generic credibility while missing whether they actually match the project’s delivery model and constraints.

Recap

  • Make-or-buy is a capability, control, and risk decision, not just a budget question.
  • Sourcing strategy should reflect uncertainty, coordination needs, and organizational capability.
  • Vendor fit matters alongside price, often more than price alone.
  • Common traps are cheapest-is-best thinking, outsource-by-default logic, and fit blindness.

Quick Check

### What is the strongest way to frame a make-or-buy decision? - [ ] As a quick choice based on whichever option is cheapest today - [x] As a decision about capability, control, speed, integration, and risk - [ ] As a purchasing-only question outside project management - [ ] As a way to avoid stakeholder involvement > **Explanation:** Strong sourcing choices consider capability and control, not just price. ### Which response is weakest? - [ ] Testing whether the work is strategically sensitive before outsourcing it - [ ] Comparing internal capability with external expertise - [x] Selecting the cheapest seller first and assuming coordination issues can be solved later - [ ] Considering how vendor choice affects schedule and integration risk > **Explanation:** Cheapest-first logic often ignores downstream risk and delivery friction. ### Why can an external vendor still be a weak choice even when technically capable? - [ ] Because vendors should never be used on projects - [ ] Because technical skill is the only factor that matters - [x] Because the vendor may still be a poor fit for coordination, governance, timing, or integration needs - [ ] Because procurement should always stay internal > **Explanation:** Capability alone is not enough if delivery fit is weak. ### When is keeping work in-house more likely to be stronger? - [ ] When confidentiality, strategic control, and close coordination all matter strongly - [ ] When the market option is clearly faster and lower risk - [ ] When the internal team has no realistic capability - [ ] When the project wants to avoid defining scope clearly > **Explanation:** High-sensitivity work with strong internal capability often belongs closer to the team. ### What is the best reason to use a sourcing strategy instead of ad hoc vendor selection? - [ ] To make the procurement paperwork longer - [ ] To guarantee the lowest bid wins - [ ] To remove the need for project governance - [x] To clarify what should be sourced, why, and how the choice affects value, risk, and coordination > **Explanation:** Sourcing strategy connects procurement to project success instead of treating it as random buying.

Sample Exam Question

Scenario: A project team needs a specialized analytics component. An internal architect says the organization could build it, but only by pulling scarce staff from other critical work. A low-cost vendor offers a quick solution, but their integration history with the organization’s platforms is weak. A second vendor costs more but has strong experience in the same environment and a better delivery record.

Question: Which response is strongest?

  • A. Choose the lowest-cost vendor because procurement should minimize direct cost first.
  • B. Keep the work in-house because using any vendor weakens project control.
  • C. Compare the sourcing options against capability, integration risk, schedule impact, and value, then select the option with the best overall project fit rather than the lowest initial price.
  • D. Delay the decision until the end of planning so the team does not have to commit early.

Best answer: C

Explanation: C is best because it applies the real make-or-buy and vendor-fit lens: capability, integration risk, schedule impact, and overall value. A overweights price. B is too absolute. D delays a decision that affects planning, dependencies, and delivery strategy.

Continue With Practice

After this section, move into bid documents, source selection, and contract types so the sourcing choice connects to actual procurement mechanics. When your practice misses come from overvaluing price and undervaluing fit, use the free PMP 2026 practice preview on web and check whether the stronger answer protected both control and delivery value.

Revised on Monday, April 27, 2026