Scribd
Upload
24 views21 pages

Lect 05-SEM

Uploaded by

Rafy Memon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views21 pages

Lect 05-SEM

Uploaded by

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

WORK BREAKDOWN STRUCTURE

LECTURE # 5
Dr. Um-e-Habiba Alvi
WORK BREAKDOWN STRUCTURE
• Dividingcomplex projects to simpler and manageable tasks is the process identified as
Work Breakdown Structure (WBS).
• Usually, the project managers use this method for simplifying the project execution.
• In WBS, much larger tasks are broken down to manageable chunks of work. These chunks can be
easily supervised and estimated.
• WBS is not restricted to a specific field when it comes to application. This methodology can be
used for any type of project management.
• Following are a few reasons for creating a WBS in a project:
• Accurate and readable project organization.
• Accurate assignment of responsibilities to the project team.
• Indicates the project milestones and control points.
• Helps to estimate the cost, time and risk.
• Illustrate the project scope, so the stakeholders can have a better understanding of the same.
WORK BREAKDOWN STRUCTURE

• WBS element may be a product, data, service, or any combination thereof.


• WBS also provides the necessary framework for detailed cost estimation and
control along with providing guidance for schedule development and control.
REPRESENTATION OF WBS

• WBS is represented as a hierarchical list of project’s work activities. There are


two formats of WBS −
• Outline View (Indented Format)
• Tree Structure View (Organizational Chart)
1. OUTLINE VIEW

• The outline view is a very user-friendly layout. It presents a good view of the
entire project and allows easy modifications as well. It uses numbers to record
the various stages of a project. It looks somewhat similar to the following −
• Software Development
ANALYSIS/SOFTWARE REQUIREMENTS
• Conduct needs analysis
• Draft preliminary software specifications
• Develop preliminary budget
• Review software specifications/budget with the team
• Incorporate feedback on software specifications
• Develop delivery timeline
• Obtain approvals to proceed (concept, timeline, and budget)
• Secure required resources
• Analysis complete
SCOPE
• Determine project scope
• Secure project sponsorship
• Define preliminary resources
• Secure core resources
• Scope complete
DESIGN
• Review preliminary software specifications
• Develop functional specifications
• Obtain approval to proceed
• Design complete
DEVELOPMENT

• Review functional specifications


• Identify modular/tiered design parameters
• Develop code
• Developer testing (primary debugging)
• Development complete
TESTING

• Develop unit test plans using product specifications


• Develop integration test plans using product specifications
TRAINING

• Develop training specifications for end-users


• Identify training delivery methodology (online, classroom, etc.)
• Develop training materials
• Finalize training materials
• Develop training delivery mechanism
• Training materials complete
DEPLOYMENT

• Determine final deployment strategy


• Develop deployment methodology
• Secure deployment resources
• Train support staff
• Deploy software
• Deployment complete
2. OUTLINE VIEW EXAMPLE
TREE STRUCTURE VIEW

• The Tree Structure View presents a very easy-to-understand view of the entire
project. The following illustration shows how a tree structure view looks like.
• This type of organizational chart structure can be easily drawn with the
features available in MS-Word.
TREE STRUCTURE VIEW EXAMPLE
TYPES OF WBS

• There are two types of WBS −


• Functional WBS − In functional WBS, the system is broken based on the
functions in the application to be developed. This is useful in estimating the
size of the system.
• Activity WBS − In activity WBS, the system is broken based on the activities
in the system. The activities are further broken into tasks. This is useful in
estimating effort and schedule in the system.
How to Make a Work Breakdown Structure

• A good Work Breakdown Structure is created using following these steps.


1. Gather Critical Documents
• Gather critical project documents.
• Identify content containing project deliverables, such as the Project Charter,
Scope Statement and Project Management Plan (PMP) subsidiary plans.

2. Identify Key Team Members


1. Identify the appropriate project team members.
2. Analyze the documents and identify the deliverables.
3. Define Level 1 Elements
• Level 1 Elements are summary deliverable descriptions that must capture 100% of
the project scope.
• Verify 100% of scope is captured.

4. Decompose (Breakdown) Elements


• Begin the process of breaking the Level 1 deliverables into unique lower Level
deliverables. This “breaking down” technique is called Decomposition.
• Continue breaking down the work until the work covered in each Element is
managed by a single individual or organization. Ensure that all Elements are
mutually exclusive.
• Ask the question, would any additional decomposition make the project more
manageable? If the answer is “no”, the WBS is done.
5. CREATE WBS DICTIONARY
• Define the content of the WBS Dictionary. The WBS Dictionary is a
narrative description of the work covered in each Element in the WBS.
The lowest Level Elements in the WBS are called Work Packages.

• Create the WBS Dictionary descriptions at the Work Package Level with
detail enough to ensure that 100% of the project scope is covered. The
descriptions should include information such as, boundaries, milestones,
risks, owner, costs, etc.
6. CREATE GANTT CHART SCHEDULE
• Decompose the Work Packages to activities as appropriate.

• Export or enter the Work Breakdown Structure into a Gantt chart for
further scheduling and project tracking.
ADVANTAGES OF ESTIMATION USING
WBS
• In WBS, the entire work to be done by the project is identified. Hence, by reviewing
the WBS with project stakeholders, you will be less likely to omit any work needed to
deliver the desired project deliverables.
• WBS results in more accurate cost and schedule estimates.
• The project manager obtains team participation to finalize the WBS. This
involvement of the team generates enthusiasm and responsibility in the project.
• WBS provides a basis for task assignments. As a precise task is allocated to a
particular team member who would be accountable for its accomplishment.
• WBS enables monitoring and controlling at task level. This allows you to measure
progress and ensure that your project will be delivered on time.
Case Study: Complex Software
System Development
• A software engineering team is embarking on a project to build a sophisticated
financial management system for a multinational corporation. The initial budget is
set at $500,000, and the project timeline is 12 months. After 6 months, the team
encounters complexities:
• Budget Spent: $300,000.
• Timeline Progress: 40%.
• The project involves intricate modules like real-time analytics, encryption
algorithms, and integration with legacy systems.
• Question: Apply Work Breakdown Structure (WBS) principles to efficiently break
down and manage the complex modules, ensuring effective coordination, timely
completion, and adherence to the remaining budget.

You might also like