Chapter 2: Defining Project Scope
Using the project charter, lessons learned, and requirements gathering techniques (such as interviews, brainstorming, focus groups, and so on), assess the detailed project requirements, assumptions, and constraints to determine project deliverables.
Deconstruct the project into a WBS in order to manage the project scope.
Everything in the project is a function of the project and product scope. Therefore, getting the scope right and managing it effectively are the best ways to ensure project success. The first step in this process is to plan how you will gather requirements, define project and product scope, organize the scope using a work breakdown structure (WBS), validate the scope with the customer, and control the scope.
Gathering requirements will transition your project from the Initiation process group into the Planning process group. If you need a refresher on process groups, review Book I, Chapter 4. Your ability to fully identify, document, organize, and control requirements and scope is the difference between a successful project and a nightmare!
After you know your requirements, then you can define the scope with a scope statement. When your scope is understood, you develop a WBS to organize the scope into deliverables. ...