Week 8 (Work Breakdown Structure) Flashcards

1
Q

Work Breakdown Schedule

A

A way in which a project may be divided by level into discrete groups for programming, cost planning and control purposes.
- a tool for defining the hierarchical breakdown of work required to deliver the products of a project.
- Major categories are broken down into smaller components. These are sub-divided until the lowest required level of detail is established (work package).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

WBS

A

shows the need for a breakdown structure to link the project to the work packages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Deliverable

A

A deliverable is a tangible or measurable result.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Stakeholders

A

Subdividing the project into tangible deliverables helps to identify the associated stakeholders and involve them in the problem solving and decision-making process. This will help stakeholders to visualize how the project will operate and what the project will look like.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Ownership

A

Subdividing the project into tangible deliverables helps to assign ownership and responsibility for its manufacture at the deliverable level, which is a key project management philosophy.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Build-Method

A

Subdividing the project into tangible deliverables helps the project manager to focus on build-method and the build sequence to the make the deliverables.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Configuration

A

Subdividing the project into tangible deliverables enables the designers to confirm configuration of the deliverables will perform as required both independently and together and will also interlink with existing facilities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Execution Strategy

A

Subdividing the project into deliverables help to align the resources (equipment and workforce) who will perform the work with deliverables.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Budget

A

Subdividing the project into tangible deliverables enables a budget to be assigned to make the deliverables. This should help to improve the cost management level of control.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Scope Creep

A

Subdividing the project into well defined deliverables helps to avoid, or certain limit, undesirable scope creep. It should be easier to confirm if a proposed change will enhance the project’s capabilities or it is just an unnecessary add on.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Transport

A

Subdividing the project into tangible deliverables helps to align the deliverables with the company’s lifting and transport capabilities and gives early warning of the need for any heavy lefts and abnormal loads.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Work Package

A

The lowest level of WBS is a work package, which is the work required to make the deliverables. The work package contains a wealth of information.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Ownership

A

Identifies who is responsible for completing the work package. This is key project management philosophy to assign ownership to all aspects of the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Description of Work

A

The description of work describes the scope of work to be completed or performed and, by implication, the work that is not included.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Number or Code

A

The work package number or code uniquely identifies the work package. This ensures that there is no confusion between similarly named work packages.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Deliverables

A

The WBS break down the scope of work into a number of tangible deliverables.

17
Q

Independent

A

Where possible, the work packages should be independent of each other so that they can be managed separately.

18
Q

Specification

A

The specifications define what the work packages need to achieve and outline the required standard.

19
Q

Quality Requirements

A

The quality requirements outline the required condition and acceptance criteria together with the level of inspection and the qualifications of the workforce. This links with the quality control plan and is an auditable item.

20
Q

Estimate (Manhours)

A

The estimate man-hours is measure of the work content per work package. If these can be scheduled, they can be rolled up to give the S curve graph, which is used in the earned value technique. Some companies limit work package to a certain number of man-hours.

21
Q

Duration

A

The work package might or might not have a duration. If the work package relates to the scope of work that will be worked on and off during the project, then the duration would be meaningless.

22
Q

Human Resources

A

Human resources identify all the people (workforce) required to complete the work.

23
Q

Procurement

A

The procurement list (bills of material, BOM) identifies all the bought-in items per work package. The procurement list is required to develop a procurement budget and delivery lead times for the procurement schedule.

24
Q

Equipment

A

The equipment list identifies all the equipment, machines and plant required to complete the work package. If special equipment is required the project manager should look for beneficial grouping.

25
Q

Similar Size

A

The work package should be a manageable size, typically between 20 to 80 man-hours. The smaller the size the more accurate the progress reporting.

26
Q

Build-Method

A

The build-method outlines how the work package will be made

27
Q

Acceptance Criteria

A

This section outlines the commissioning and testing that is required to validate and verify the work packages before handing over to the client for operation.

28
Q

Assumptions and Constraints

A

The assumptions and constraints can be identified at the wok package level to help define the boundaries of the project.

29
Q

Activities

A

A list of activities can be developed form each of the work packages as required by the CPM analysis and Gantt chart scheduling.

30
Q

Risk

A

The level of risk can be identified at the work package level, which will enable the project manager to develop mitigation responses at the appropriate level. The level of risk should not be noted and compared with the corporate acceptable level of risk.

31
Q

Location Breakdown Structure

A
  • focuses on the physical location of the work.
  • appropriate for a project that has items of work at many different sites, buildings and premises.
32
Q

Transport breakdown structure

A
  • Size
  • weight
  • configuration
  • upgrade
  • disposal