Develop and Manage Project Scope

Before a single line of code is compiled or a single foundation poured, a boundary must be drawn around the endeavor. In physics, if you fail to define the boundary of a thermodynamic system, you cannot calculate the energy entering or leaving it. In project management, this boundary represents the difference between a controlled, successful delivery and a chaotic, endless march of changing expectations. We must distinguish immediately between two fundamentally different types of boundaries. Product scope represents the features and functions that characterize a product, service, or result—the exact software specifications or the physical dimensions of a bridge. Project scope, however, is the work performed to deliver a product, service, or result with the specified features and functions. One is the physical destination; the other is the exertion required to arrive there.

In both physics and project management, defining a clear system boundary is essential to measure and control what enters or leaves the endeavor.
In both physics and project management, defining a clear system boundary is essential to measure and control what enters or leaves the endeavor.

Mastering project scope requires you to translate ambiguous stakeholder desires into concrete, executable boundaries, break that work down into manageable pieces, and rigorously defend those pieces against uncontrolled expansion.