See Description

Work breakdown structure

WBS

Columbia Southern University

Tiffany Williams

The work breakdown structure is a key project deliverable that organizes the team's work into

manageable sections. Is a "deliverable oriented hierarchical decomposition of the work to be executed

by the project team." The work breakdown structure visually defines the scope into manageable chunks

that a project team can understand, as each level of the work breakdown structure provides further

definition and detail. (Work Breakdown Structure (WBS). (n.d.). Retrieved from

https://www.workbreakdownstructure.com)IN this case, I would use a three level work breakdown to

illustrate the processes in the construction project. In the paper am going to outline the work break

down structure for the construction project of a warehouse showing the various stages, participants, the

budget, as well as project timeline and constraints.

The depiction of the WBS will be using both charts and tables indicating codes for the various activities.

The idea process can be illustrated in the diagram below together with the OBS

WBS #: 1.1.1 Task: Create Plan

Est. Level of

Effort:

40 hrs Owner: Project Manager

Resources Needed: Subject Matter Experts Work

Products:

MS Project Plan

Description of

Task:

Development of a detailed project plan that lists all key resources,

tasks, milestones, dependencies, and durations.

Input: 1. Approved Project Charter 2. SMEs

Dependencies: 3. Approval of Budget

Risk: 4. Changes to IT Apps plans and deliverables 5. IT Apps implementation releases, which conflict with

implementation

WBS #: 1.1.2 Work Item: Make Budget

Est. Level of

Effort:

16 hrs. Owner: Project Manager

Resources Needed: CFO, CIO, Executive

Sponsor

Work

Products:

ITPR

Description of

Task:

Development and documentation of the project budget based on

plan and resources.

Input: 6. Approved Project Charter 7. SMEs

Dependencies: 8. Approval of Project Charter

Risk: 9. Collapse of house

WBS FIELDS

WBS

# Task Description of Task

Work

Products Owners

Est. Level

of Effort

1 PLANNIN

G

All task management and

management activities

1.1 Plan and

Supervise

Roll-up Task Project

Manager

N/A

1.1.

1

Create Plan Development of WBS, work

package identification,

schedule formulation,

staffing projection, resource

estimation. Followed by

development of a detail

project plan that list all the

key resources, task,

milestones, dependencies,

and duration.

WBS,

WBS

Dictionary,

MS Project

Plan

Project

Manager

40 hrs

1.1.

2

Create

Budget

Development and

documentation of the project

budget based on plan and

resources

ITPR Project

Manager

40 hrs

1.1.

3

Prepare

Disburseme

nt /

Reconciliati

on

Development of

disbursement process for the

project including

acceptance/approval forms.

Purchase

Orders,

Deliverable

Product

Acceptance

Form

CFO 40 hrs

1.1.

4

Coordinate

Activities

Ongoing planning activities

for the project including

weekly meetings

Meeting

Minutes

Project

Manager

8 hrs/week

Tabular View

The Tabular View is a nicely organized table view of the WBS. It is a good option

for organizations which prefer table formats.

Level 1 Level 2 Level 3

1 Widget Management

System

1.1 Initiation 1.1.1 Evaluation & Recommendations

1.1.2 Develop Project Charter

1.1.3 Deliverable: Submit Project

Charter

1.1.4 Project Sponsor Reviews Project

Charter

1.1.5 Project Charter Signed/Approved

1.2 Planning 1.2.1 Create Preliminary Scope

Statement

1.2.2 Determine Project Team

1.2.3 Project Team Kickoff Meeting

1.2.4 Develop Project Plan

1.2.5 Submit Project Plan

1.2.6 Milestone: Project Plan Approval

1.3

Execution

1.3.1 Project Kickoff Meeting

1.3.2 Verify & Validate Requirements

1.3.3 Design map layout of warehouse

1.3.4 Procure materials for construction

1.3.9 Commence construction

1.4 Control 1.4.1 Project Management

1.4.2 Project Status Meetings

1.4.3 Risk Management

1.4.4 Update Project Management Plan

1.5 Closeout 1.5.1 Audit Procurement

1.5.2 Document Lessons Learned

1.5.3 Update Files/Records

1.5.4 Gain Formal Acceptance

1.5.5 Archive Files/Documents

In tabular form the WBS for the project is represented below with codes

Level WBS Code Element Name

1 1 Widget Management System

2 1.1 Initiation

3 1.1.1 Evaluation & Recommendations

3 1.1.2 Develop Project Charter

3 1.1.3 Deliverable: Submit Project Charter

3 1.1.4 Project Sponsor Reviews Project Charter

3 1.1.5 Project Charter Signed/Approved

2 1.2 Planning

3 1.2.1 Create Preliminary Scope Statement

3 1.2.2 Determine Project Team

3 1.2.3 Project Team Kickoff Meeting

3 1.2.4 Develop Project Plan

3 1.2.5 Submit Project Plan

3 1.2.6 Milestone: Project Plan Approval

2 1.3 Execution

3 1.3.1 Project Kickoff Meeting

3 1.3.2 Verify & validation

3 1.3.3 Design map of the warehouse

3 1.3.4 Procure construction materials

3 1.3.5 Commence construction

3 1.3.6 Monitor progress

3 1.3.7 Access if project completion meets standards

3 1.3.8 Orientation of employees

3 1.3.9 Execute operation

2 1.4 Control

3 1.4.1 Project Management

3 1.4.2 Project Status Meetings

3 1.4.3 Risk Management

3 1.4.4 Update Project Management Plan

2 1.5 Closeout

3 1.5.1 Audit Procurement

3 1.5.2 Document Lessons Learned

3 1.5.3 Update Files/Records

3 1.5.4 Gain Formal Acceptance

3 1.5.5 Archive Files/Documents

The chart below illustrates the steps in the actual construction process

An easy way to think about the work breakdown structure is like an outline or map of our project. A

work breakdown structure starts with the project as the top level deliverable and is further decomposed

into sub-deliverables using the outline hierarchy as above

The undertaking group makes the work breakdown structure by recognizing the major practical

deliverables and subdividing those deliverables into littler frameworks and sub-deliverables. These sub-

deliverables are further decayed until a solitary individual can be relegated. At this level, the particular

work bundles needed to create a sub- deliverable are distinguished and assembled together. The work

bundle speaks to the rundown of undertakings or "to-dos" to create the particular unit of work. In the

event that you've seen point by point undertaking calendars, then you'll perceive the assignments under

the work bundle as the "stuff" individuals need to finish by a particular time and inside a particular level

of exertion.

From an expense viewpoint, these work bundles are gathered and doled out to a particular division to

deliver the work. These offices or expense records are characterized in a hierarchical breakdown

structure and are allotted a financial plan to deliver the particular deliverables. By coordinating the

expense accounts from the hierarchical breakdown structure and the venture's work breakdown

structure, the whole association can track budgetary advancement notwithstanding extend execution.

Finally the project timeline and completion dates are as shown below

Activities Dependencies Resources Activity

duration

days

Start date Due date

Project start

date

A Initiation Project

officer

7 1 st Dec

2014

7 th

Dec

2015

B Planning Project

office

7 8 th

Dec

2014

14 th Dec

2015

C Execution B IT 4 15 th Dec 18

th Jan

2-15

2014

D Monitoring

and control

A,B.C IT 7 19 th Jan

2015

25 th Jan

2015

E Closing A,B,C,D Project team 6 26 th Jan

2015

31 st Jan

2015