Work Breakdown Structure

Question 1

What is a work breakdown structure used
for?

Answer 1

1. The WBS is the entry data needed to produce a time
   schedule or a cost schedule.
2. The WBS can also be used as entry data for
   performance management & control or for
   procurement (contracts or purchasing) planning.
3. The concept of “levels” is important. It allows the
   Manager to designate the level of detail required (or
   available) to describe the project. 12

Question 1

What is a Work Breakdown Structure ?
6

Answer 1

• The WBS consists of a logical collection of project
  work items or project deliverables.
• The concept involves dividing a project into
  manageable pieces that can be individually planned,
  estimated and controlled.
• The WBS provides a map of what is to be provided,
  but it has no time or cost dimension.

Question 2

what are the formats ?

Answer 2

Hireachy, Tabular List

Question 3

Hireachy is:

Answer 3

Hierarchy: This format resembles an organizational chart, visually representing the project’s breakdown into major work items and their supporting sub-items. This structure makes it easy to see the relationships between different parts of the project and how they contribute to the overall goal.

Question 4

Tabular is:

Answer 4

●
Tabular: This format presents the WBS in a table, with columns representing different levels of detail and rows listing the specific work items. This format can be helpful for larger projects with a significant number of work packages, allowing for clear organization and tracking of each element.

Question 5

List is:

Answer 5

This format outlines the project breakdown as a sequential list, breaking down the project into increasingly detailed sub-items. It emphasizes a logical progression through the project, which can be helpful for planning and scheduling activities

Question 6

WBS Contents include

Answer 6

1. Planning deliverables.
2. Pre‐design deliverables.
3. Design deliverables.
4. Approvals.
5. Supply deliverables.
6. Project establishment deliverables or works.
   7.Pre‐construction or advance works.
7. Construction works.
8. Testing & commissioning deliverables
9. Deliverables required at interfaces
   between the above work items.
10. Activities added at lower levels to
    describe how deliverables will be
    delivered ( for clarity).

Question 7

Sources of Information for WBS:

Answer 7

○
Experienced planning and project engineers.
○
Professional cost estimators and programmers.
○
Senior construction and design engineers.
○
Documentation from similar past projects (conference papers, reports).
○
Organizational and industry guidelines (manuals, standards).

Question 8

Starting a WBS:

Answer 8

○
Choose a format: Hierarchy, tabular, list.
○
Generic Headings: Consider common project elements like approvals, procurement, site establishment, underground services, foundations, structures, fit-out, testing, commissioning, and site cleanup.
○
Tailor Headings: Adjust for project type (civil, electrical/mechanical) and specific requirements.

○
Use Existing Data: Deconstruct previous critical path programs or cost estimates for similar projects to identify potential headings.

Question 9

Evolution Through Project Stages:

Answer 9

Pre-feasibility and Feasibility: WBS helps define the project scope, enabling the assessment of time, cost, and economic viability.
○
Functional Design and Business Case: More detailed WBS supports decision-making on project continuation.
○
Delivery: WBS becomes critical for:
■
Detailed design and procurement.
■
Creating contract packages and identifying work packages for tenders.
■
Construction planning, scheduling, and risk assessment.
○
Completion: WBS facilitates:
■
Creation of as-built drawings.
■
Project reviews and identification of areas for improvement.