A WBS lists the project tasks, identified by a unique identifier, in the order that they will be performed. All of these statements are true about a work breakdown structure (wbs) except: - A WBS lists the project tasks, identified by a unique identifier, in the order that they will be performed. a work breakdown structure (wbs) is a hierarchical chart representing the total work for a project. The WBS is created during scope definition by the project manager and team.
In creating a WBS, the major deliverables of the project are defined. Then, each deliverable is decomposed into smaller pieces, with the lowest level being a work package. While the wbs does identify each task with a unique identifier, the tasks listed in a WBS are not in the order that they will be performed. These activities are sequenced later in the planning process. The WBS can be used to estimate resource requirements. The WBS is used as input to many other project processes.
Project managers use the WBS as a tool to estimate project costs, activity durations, and resource requirements. A WBS breaks down a project into smaller activities that can be successfully estimated. It is possible during decomposition to break a project into an excessive number of work packages. The rule of thumb is that each work package is small enough to be able to estimate time and costs for the activity and effectively manage the activity. The WBS documents the scope of the project by identifying all work that will be performed. Work not included in the WBS is not in project scope.