4.2. Develop and Manage Project Scope

💡 First Principle: Scope isn't "whatever's in the charter" — it's actively defined, agreed to, and broken down into a shared, unambiguous understanding, because vague scope is where schedule and cost overruns actually originate.

Enablers: define scope, obtain stakeholder agreement on scope, and break down scope (into a WBS, backlog, or equivalent decomposition depending on approach).

Obtaining explicit stakeholder agreement — not just documenting scope and assuming buy-in — is the enabler most commonly missed in practice and most commonly tested: a scope statement that was written and circulated but never explicitly confirmed with the key stakeholder is a documented scope in name only.

⚠️ Exam Trap: Treating scope as fully "managed" once it's written down. If a scenario shows disagreement or confusion surfacing later about what's included, the root cause PMI is testing for is usually "agreement was never actually obtained," not "the document was unclear."