Estimate the Scope of the Project

The WBS evolves with the project. Initially a top-level WBS can serve to structure the initial estimating. The development of a WBS divides the overall project into an interconnected set of manageable components. The WBS is typically a product-oriented structure that provides a scheme for identifying and organizing the logical units of work to be managed, which are called “work packages.” The WBS provides a reference and organizational mechanism for assigning effort, schedule, and responsibility and is used as the underlying framework to plan, organize, and control the work done on the project.

• Develop a WBS based on the product architecture. The WBS provides a scheme for organizing the project’s work around the products that the work supports. The WBS should permit the identification of:
  • Identified risks and their mitigation tasks
  • Tasks for deliverables and supporting activities
  • Tasks for skill and knowledge acquisition
  • Tasks for development of needed support plans, such as configuration management, quality assurance, and verification plans
  • Tasks for integration and management of non-developmental items
• Identify the work packages in sufficient detail to specify estimates of project tasks, responsibilities, and schedule. The top-level WBS is intended to help in gauging the project work effort in terms of tasks and organizational roles and responsibilities. The amount of detail in the WBS at this more detailed level helps in developing realistic schedules, thereby minimizing the need for management reserve.
• Identify work products (or components of work products) that will be externally acquired.
• Identify work products that will be reused.