Create WBS ( work breakdown structure ) is the process of breaking down project outputs and work into smaller pieces that are easier to handle. Most importantly, this process gives you a plan for what you need to deliver. This step is either done only once or at set times during the job. below Figure shows what make and building a work breakdown structure process takes in, the tools and methods it uses, and what it comes out of.
The Work Breakdown Structure (WBS) shows the comprehensive list of tasks that the project team needs to complete in order to meet the project goals and produce the needed outputs. The work breakdown structure (WBS) manages and describes the whole project’s scope. It shows the tasks listed in the accepted project scope statement.
Work packages are the smallest WBS components that hold the planned work. Work that needs to be planned, estimated, tracked, and managed can be put together in a work package. When used in the WBS, “work” refers to the deliverables or work items that come from an activity, not the activity itself.
Create WBS: Inputs
Project Management Plan
The scope management plan is an example of a project management plan component, but it’s not the only one. To make the WBS from the project scope statement, the scope management plan explains how to do it.
Project Documents
in create and building a work breakdown structure ( WBS ). process can use the following types of project documents, but not only those listed below: The project plan statement lists the tasks that will be done and the ones that won’t be. Documentation of requirements, A detailed list of objectives shows how each one meets the project’s business needs.
Enterprise Environmental Factors
Some enterprise environmental factors that might affect the Create WBS process are industry-specific WBS standards that are important to the project, but they are not the only ones. The WBS could be based on these industry-specific guidelines.
Organizational Process Assets
You can use organizational process assets to change the Create WBS process. These can be policies, methods, and templates for the WBS; project files from previous projects; and lessons learned from previous projects.
Create WBS : Tools And Techniques
Expert Judgment
Advice from people or groups who know about or have worked on similar projects before should be considered in create and building a work breakdown structure.
Decomposition
Decomposition is a way to break up the project scope and outputs into smaller pieces that are easier to handle. At the lowest level of the WBS, the work that can be evaluated in terms of cost and time is called a “work package.” The amount of decomposition is often based on how much control is needed to run the project well. How detailed work packages are will depend on how big and complicated the job is. Breaking up the whole project into work packages usually includes the following steps:
- Identifying and analyzing the deliverables and related work,
- Structuring and organizing the WBS,
- Decomposing the upper WBS levels into lower-level detailed components,
- Developing and assigning identification codes to the WBS components, and
- Verifying that the degree of decomposition of the deliverables is appropriate
Create WBS : Outputs
Scope Baseline
The scope baseline is the accepted version of the scope statement, WBS, and WBS dictionary that goes with it. It can only be changed through formal change control processes and is used to compare other versions. It’s part of the plan for managing the project. Some parts of the scope baseline are :
Project scope statement.
There is a description of the project scope, important deliverables, assumptions, and constraints in the project scope statement.
WBS
The Work Breakdown Structure (WBS) shows the comprehensive list of jobs that the project team needs to complete in order to meet the project goals and produce the needed outputs. The work breakdown structure (WBS) gets more detailed as you go down the levels.
Work package
There is a work package with a unique number at the very bottom of the WBS. These numbers make up a code of accounts and make it possible to sum up prices, schedules, and resource information in a hierarchical way.
A master account holds each work package. The management uses a control account to keep an eye on the project’s scope, price, and schedule, and compares them to the earned value to see how well the project is going. Each work package is linked to a different control account, but a control account has more than one work package.
Planning package
One or more planning items may be part of the control account. A planning package is a part of the work breakdown structure that comes after the control account and before the work package. It has known work content but no specific schedule activities.
WBS dictionary
A document called the WBS dictionary lists in great depth the deliverables, activities, and schedules for each part of the WBS. The WBS dictionary is a piece of paper that goes with the WBS. The WBS dictionary has a lot of information that was made by other methods and then added to this document later. Some examples of information that could be in the WBS definition in Create WBS ( work breakdown structure ) process are the following :
- Code of account identifier,
- Description of work,
- Assumptions and constraints,
- Responsible organization,
- Schedule milestones,
- Associated schedule activities,
- Resources required,
- Cost estimates,
- Quality requirements,
- Acceptance criteria,
- Technical references, and
- Agreement information.
Project Documents Updates
- Assumption log : There are more assumptions or limits added to the assumption log after the Create WBS process.
- Requirements documentation : Updates to the requirements documentation can include accepted changes made during the Create WBS process.
References :