Scribd
Upload
336 views

Template Work Breakdown Structure 2011-11-08

The document outlines a work breakdown structure (WBS) for a project. The WBS breaks down the project into seven main work packages including initiation, requirements and analysis, design, development, testing, implementation, and post-implementation. It further breaks down each work package into lower level tasks with estimates for effort, complexity, dependencies, and owners. The WBS is intended to help communicate and plan the work required to complete the project aligned with the system development life cycle.

Uploaded by

seanjustine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
336 views

Template Work Breakdown Structure 2011-11-08

The document outlines a work breakdown structure (WBS) for a project. The WBS breaks down the project into seven main work packages including initiation, requirements and analysis, design, development, testing, implementation, and post-implementation. It further breaks down each work package into lower level tasks with estimates for effort, complexity, dependencies, and owners. The WBS is intended to help communicate and plan the work required to complete the project aligned with the system development life cycle.

Uploaded by

seanjustine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Work Breakdown

Structure
[Insert Project Name Here]

Type Author Name Here


Last Updated: Month day, Year
Introduction
The Work Breakdown Structure (WBS) is a view into the project showing the work packages. It is a tool
which 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. There are many ways a WBS can be presented. This can be customized based on the project need.
The Work Breakdown Structure presented here represents all the work required to complete this
project.

A feneral rule for developing WBS is the 8 to 80 rule (where the WBS is broken down to where a work
package contains between 8 and 80 hours of work to complete).

The WBS for this project will be more aligned with the System Development Life Cycle (SDLC) rather
than focusing on the project management process groups. This WBS will help the team to understand
the overall picture of what is going to happen next, without having to be familiar with the project
management processes.
Work Breakdown Structure (WBS) – [Project Name]

Work Breakdown Structure

Project Name

2 Requirement 7 Post
1 Initiation & Analysis
3 Design 4 Development 5 Test 6 Implementation Implementation

2.3 Determine and 4.1 Technical


2.1 Gather Inssue/ 3.1 Alternative 5.1 Functional Unit 6.1 Communication 7.1 Conduct survey
1.1 Business Case 2.2 Focus Group document the Specification
Concern graphical design Testing to the users of new system
reuirements Document

1.2 Evaluation & 2.2.1 Selection of 4.2 Development & 5.2 Quality check/ 6.2 User training & 7.1 Update file/
2.1.1 Survey Results 3.2 Prototype
recommendations focus group unit testing verification documentation documents

2.1.2 Analyze the 3.3 Finalize 5.3 Integration 6.3 Initiate support
1.3 Project Charter 2.2.2 Kick off 7.3 Close project
RT queue functional design Testing/ UAT & maintenance plan

1.4 Project 6.4 System


2.1.3 analyze help 2.2.3 Prototype
Management implementation/
emails review
Planning Go-live

1.5 Project
2.1.4 Presentation 2.2.4 Final review
Schedule

2.1.5 Investigate
the other systems

3|Page
[Insert full path and file name]
WBS Dictionary

WBS Id WBS Name Include Complexity Estimated Effort Dependency Owner


(Completion
Criteria)
1.0 Initiation
1.1 Business case Business case Low 16hrs None Name
documented
1.2 Evaluation & Case is fully Low 8hrs 1.1 Name
Recommendation evaluated by
HRMS
management
team
1.3 Project Charter Charter signed Medium 16hrs 1.2 Name
written and
approved
1.4 Project Includes the High 70hrs 1.3, 2.3 Name
Management scope
Planning management
plan, time
management
plan, Risk
management
plan, HR Plan
1.5 Project Schedule Activities/Task Medium/ High 16hrs 1.4, 2.3, 3.0 Name
identified
dependencies
identified, dates
and resources
allocated.
2.0 Requirement &
Analysis
WBS Id WBS Name Include Complexity Estimated Effort Dependency Owner
(Completion
Criteria)
2.1 Gather Publish survey,
Issue/Concern one on one
conversation,
presentations to
staff, collecting
feedback. All
issues and
concerns are
compiled.
2.1.1 Survey result Publish and Medium 16hrs None Name
categorize survey
2.1.2 Analyze the RT RT queues are Medium 16hrs None Name
queues compiled and
categorized.
2.1.3 analyze help Emails Medium 7hrs None Name
emails categorized and
compiled.
2.1.4 Presentation Feedbacks from Medium 7hrs None Name
presentations are
compiled.
2.1.5 Investigate the Look at how other Medium 4hrs None Name
other systems institutions have
delivered
functionality
2.2 Focus Group
2.2.1 Selection of focus Analyze Medium 4hrs 2.1.1, 2.1.4 Name
group volunteers and
send targeted
emails to get
representative
sample of
WBS Id WBS Name Include Complexity Estimated Effort Dependency Owner
(Completion
Criteria)
managers and
employee
2.2.2 Kick off Introduce project Medium 12hrs 2.2.1 Name
to focus group,
results to date

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy