Work Breakdown Structure (WBS) : Create WBS: Inputs, Tools & Techniques, and Outputs

Lecture 6 29/04/2019 Work Breakdown Structure (WBS) by:Asmar.
Work Breakdown Structure (WBS)

Create WBS is the process of subdividing project deliverables and project work into
smaller, more manageable components.The key benefit of this process is that it provides a
structured vision of what has to be delivered.
Figure 1:Create WBS: Inputs, Tools & Techniques, and Outputs
The WBS is a hierarchical decomposition of the total scope of work to be carried out by the
project team to accomplish the project objectives and create the required deliverables. The
WBS organizes and defines the total scope of the project, and represents the work specified
in the current approved project scope statement.
The planned work is contained within the lowest level of WBS components, which are
called work packages. A work package can be used to group the activities where work is
scheduled and estimated, monitored, and controlled. In the context of the WBS, work refers
to work products or deliverables that are the result of activity and not to the activity itself.
Work breakdown structures advantages

What are the main advantages and benefits of creating a WBS?
 Focuses on end goals and organizes details

 Visually represents all parts of a project
 Breaks the work into manageable parts
 Provides an ongoing view of how the entire project is progressing for management and
team members
 Helps to predict results based on various scenarios
 Determines measurable outcomes
 Ensures no overlap and no gaps in responsibility
 Allows to make successful experiences repeatable
 Sets a foundation for estimating costs
 Improves team productivity
Lecture 6 29/04/2019 Work Breakdown Structure (WBS) by:Asmar.K
 Helps to describe the project scope to stakeholders
 Increases communication and enables more creativity and brainstorming
 Helps in managing risks
 Provides teams flexibility
 Eliminates confusion
 Helps write and support the statement of work
Create WBS :Inputs
1.1 Scope Management Plan
The scope management plan is a component of the project or program management plan
that describes how the scope will be defined, developed, monitored, controlled, and verified.
The scope management plan is a major input into the Develop Project Management Plan
process, and the other scope management processes. It is management plan specifies how to
create the WBS from the detailed project scope statement and how the WBS will be
maintained and approved.
1.2 Project Scope Statement
The project scope statement is the description of the project scope, major deliverables,
assumptions, and constraints. The project scope statement documents the entire scope,
including project and product scope. It describes, in detail, the project’s deliverables and the
work required to create those deliverables.
The project scope statement describes the work that will be performed and the work that is
excluded. It also lists and describes the specific internal or external restrictions or
limitations that may affect the execution of the project.
1.3 Requirements Documentation
Requirements documentation describes how individual requirements meet the business need
for the project . Requirements may start out at a high level and become progressively more
detailed as more about the requirements is known.
Detailed requirements documentation is essential for understanding what needs to be

produced as the result of the project and what needs to be done to deliver the project and its
final products.
1.4 Enterprise Environmental Factors
Enterprise environmental factors refer to conditions, not under the control of the project
team, that influence, constrain, or direct the project. Enterprise environmental factors are
considered inputs to most planning processes, may enhance or constrain project
management options, and may have a positive or negative influence on the outcome.
1.5 Organizational Process Assets
The organizational process assets that can influence the Create WBS process include, but
are not limited to:
 Policies, procedures, and templates for the WBS;

 Project files from previous projects; and
 Lessons learned from previous projects.
2 -Create WBS: Tools and Techniques
2.1 Decomposition
Decomposition is a technique used for dividing and subdividing the project scope and
project deliverables into smaller, more manageable parts. The work package is the work
defined at the lowest level of the WBS for which cost and duration can be estimated and
managed. The level of decomposition is often guided by the degree of control needed to
effectively manage the project. The level of detail for work packages will vary with the size
and complexity of the project. Decomposition of the total project work into work packages
generally involves the following activities:
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.
A portion of a WBS with some branches of the WBS decomposed down through the work
package level is shown in Figure 2
Figure 2: Sample WBS Decomposed Down Through Work Packages
2.2 Expert Judgment
Expert judgment is often used to analyze the information needed to decompose the project
deliverables down into smaller component parts in order to create an effective WBS. Such
judgment and expertise is applied to technical details of the project’s scope and used to
reconcile differences in opinion on how to best break down.
the overall scope of the project. This level of expertise is provided by any group or
individual with relevant training, knowledge, or experience with similar projects or business
areas. Expert judgment can also come in the form of predefined templates that provide
guidance on how to effectively break down common deliverables. Such templates may be
industry or discipline specific or may come from experience gained in similar projects. The
project manager, in collaboration with the project team, then determines the final
decomposition of the project scope into the discrete work packages that will be used to
effectively manage the work of the project.
Create WBS: Outputs
3.1 Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure
(WBS), and its associated WBS dictionary, that can be changed only through formal
change control procedures and is used as a basis for comparison. It is a component of the
project management plan. Components of the scope baseline include:
 Project scope statement. The project scope statement includes the description of the
project scope, major deliverables, assumptions, and constraints.
 WBS. The WBS is a hierarchical decomposition of the total scope of work to be carried
out by the project team to accomplish the project objectives and create the required
deliverables. Each descending level of the WBS represents an increasingly detailed
definition of the project work
 WBS dictionary. The WBS dictionary is a document that provides detailed deliverable,
activity, and scheduling information about each component in the WBS. The WBS
dictionary is a document that supports the WBS. Information in the WBS dictionary may
include, but is not limited to:
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.
3.2 Project Documents Updates

Project documents that may be updated include, but are not limited to, requirements
documentation, which may need to be updated to include approved changes. If approved
change requests result from the Create WBS process,
then the requirements documentation may need to be updated to include approved changes.

Work Breakdown Structure (WBS) : Create WBS: Inputs, Tools & Techniques, and Outputs

Uploaded by

Copyright:

Available Formats

Work Breakdown Structure (WBS) : Create WBS: Inputs, Tools & Techniques, and Outputs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Work Breakdown Structure (WBS) : Create WBS: Inputs, Tools & Techniques, and Outputs

Uploaded by

Copyright:

Available Formats

Lecture 6 29/04/2019 Work Breakdown Structure (WBS) by:Asmar.

Work Breakdown Structure (WBS)

Figure 1:Create WBS: Inputs, Tools & Techniques, and Outputs

Work breakdown structures advantages

 Focuses on end goals and organizes details

Create WBS :Inputs

1.1 Scope Management Plan

1.2 Project Scope Statement

1.3 Requirements Documentation

Detailed requirements documentation is essential for understanding what needs to be

1.5 Organizational Process Assets

 Policies, procedures, and templates for the WBS;

2 -Create WBS: Tools and Techniques

Identifying and analyzing the deliverables and related work;

Figure 2: Sample WBS Decomposed Down Through Work Packages

2.2 Expert Judgment

Create WBS: Outputs

3.1 Scope Baseline

3.2 Project Documents Updates

You might also like