W B S (WBS) : ORK Reakdown Tructure
W B S (WBS) : ORK Reakdown Tructure
(WBS)
DRONETECH
REV: 0
INTRODUCTION
The WBS is a view into the project which shows what work the project encompasses. In which
it helps to easily communicate the work and processes involved to execute the project. The
Project Manager and project team use the WBS to develop the project schedule, resource
requirements and costs.
1
OUTLINE VIEW
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 User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
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
2
HIERARCHICAL STRUCTURE
3
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.
4
TREE STRUCTURE VIEW
Drone to Home
Delivery
Prototype
1
Develop Project Determine Project Verify & Validate Project Status Document Lessons
Charter Team User Requirements Meetings Learned
1.1.2 1.2.2 1.3.2 1.4.2 1.5.2
User Training
1.3.8
Go Live
1.3.9
5
WBS DICTIONARY
The WBS Dictionary contains all the details of the WBS which are necessary to successfully
complete the project. Most importantly it contains a definition of each Work Package which can
be thought of as a mini scope statement. Resources on the project will look at the WBS
6
3 1.3.1 Project Manager conducts a formal kick
off meeting with the project team,
project stakeholders and project
Project Kickoff Meeting sponsor.
3 1.3.2 The original user requirements is
reviewed by the project manager and
team, then validated with the
Verify & Validate User users/stakeholders. This is where
Requirements additional clarification may be needed.
3 1.3.3 The technical resources design the new
Design System widget management system.
3 1.3.4 The procurement of all hardware,
software and facility needs for the
Procure Hardware/Software project.
3 1.3.5 Team installs a development system for
testing and customizations of user
Install Development System interfaces.
3 1.3.6 The system is tested with a select set of
Testing Phase users.
3 1.3.7 The actual system is installed and
Install Live System configured.
3 1.3.8 All users are provided with a four hours
training class. Additionally, managers
are provided with an additional two
User Training hours class to cover advanced reporting.
3 1.3.9 Go Live System goes live with all users.
2 1.4 The work involved for the control
Control process of the project.
3 1.4.1 Overall project management for the
Project Management project.
3 1.4.2 Project Status Meetings Weekly team status meetings.
3 1.4.3 Risk management efforts as defined in
Risk Management the Risk Management Plan.
3 1.4.4 Project Manager updates the Project
Management Plan as the project
Update Project Management Plan progresses.
2 1.5 Closeout The work to close-out the project.
3 1.5.1 An audit of all hardware and software
procured for the project, ensures that all
procured products are accounted for and
Audit Procurement in the asset management system.
3 1.5.2 Project Manager along with the project
team performs a lessons learned
meeting and documents the lessons
Document Lessons Learned learned for the project.
7
3 1.5.3 All files and records are updated to
Update Files/Records reflect the widget management system.
3 1.5.4 The Project Sponsor formally accepts
the project by signing the acceptance
Gain Formal Acceptance document included in the project plan.
3 1.5.5 All project related files and documents
Archive Files/Documents are formally archived.
GLOSSARY OF TERMS
Level of Effort:
Level of Effort (LOE) is how much work is required to complete a task.
WBS Code: A unique identifier assigned to each element in a Work Breakdown
Structure for the purpose of designating the elements hierarchical location
within the WBS.
Work Package: A Work Package is a deliverable or work component at the lowest level of
its WBS branch.
WBS Component: A component of a WBS which is located at any level. It can be a Work
Package or a WBS Element as there's no restriction on what a WBS
Component is.
WBS Element: A WBS Element is a single WBS component and its associated attributes
located anywhere within a WBS. A WBS Element can contain work, or it
can contain other WBS Elements or Work Packages.