4.2.2. Acquire and Build
💡 First Principle: Acquire is about obtaining what you don't already have; build is about creating and assembling the actual components — the "get the parts, make the thing" pair.
The purpose of acquire is to obtain the resources, components, and capabilities needed — whether by buying, licensing, or sourcing from partners and suppliers. The purpose of build is to create, develop, and assemble the product or service components into something that works, integrating acquired and created elements.
⚠️ Exam Trap: Acquire isn't only "procurement of hardware" — it covers obtaining any needed resource or capability, including from partners. Build is creation/assembly, distinct from the later move into production (transition).
Reflection Question: Why does ITIL separate "acquire" from "build" rather than lumping them as "make it"?
