Make-or-Buy Analysis

A structured approach to collect and organize product requirements, then evaluate viable options to decide whether to purchase the item from an external vendor or manufacture it within the organization.

Key Points

  • Compares external procurement versus in-house production to meet project needs.
  • Assesses total lifecycle costs, including acquisition, operations, maintenance, and disposal.
  • Considers schedule, quality, risk, capacity, and organizational expertise.
  • Guides the procurement strategy and documentation in the procurement management plan.

Example

A hardware project requires custom metal brackets. The team gathers specifications, estimates internal fabrication effort, and requests quotes from suppliers. Analysis shows a qualified vendor can deliver sooner with lower total cost and acceptable quality, so the project opts to buy rather than make.

PMP Example Question

While planning procurements, the team compiles product requirements and compares building a component internally versus purchasing a commercial alternative to meet a tight deadline. What technique are they using?

  1. Make-or-buy analysis
  2. Bidder conference
  3. Source selection criteria
  4. Procurement performance review

Correct Answer: A — Make-or-buy analysis

Explanation: Make-or-buy analysis evaluates whether to procure from an external supplier or produce in-house by comparing requirements, costs, schedule, risks, and capabilities.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management and Technology offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More