Software Project Management

Work Breakdown Structure

TOTAL SCOPE OF THE PROJECT
 Total Scope of The Project
Total Scope: The sum of the products, services, and results to be
provided as a project. There are two scopes within project
management:
Product Scope Project Scope
The product scope describes, lists, The project scope describes the work
and categorizes all the features and that must be completed in order to
components of the finished complete the project.
deliverable - The things the customer
sees.
 Project Scope vs Product Scope
Each scope depends on the other, and what happens in either
scope affects the other.

When the stakeholders agree on the product scope, then you

can focus on creating the software project scope.
WORK BREAKDOWN STRUCTURE
 Work Breakdown Structure
Work Breakdown Structure (WBS) is a hierarchical
decomposition of the total scope of work to be carried out by
the project team to accomplish the project objectives and create
the required deliverables.
• It includes things (deliverables, components, etc.) and not activities.
 Work Breakdown Structure
• WBS breaks down the project into smaller components,
making the project less overwhelming and more manageable.

• By using a WBS, the various individuals and teams can focus

on their specific tasks and deliverables while also seeing how
their piece fits into the project.

• WBS is an excellent tool for measuring project completion,

identifying milestones and allocating budget resources.
Work Breakdown Structure
 Include Deliverables Not Activities
• According to PMBoK, deliverable is “any unique and verifiable
product, result, or capability to perform a service that is required
to be produced to complete a process, phase, or project”.

• According to PMBoK, work refers to “work products or deliverables

that are the result of effort and not the effort itself”.

• That is, “work” defines the end-result of any activity.

• The work remains constant even though the amount of effort

needed to get there might inflate/deflate.
 How To Create WBS?
• Gather Critical Documents
• Identify Key Team Members
• Define Major Deliverables
• Decompose (Breakdown) Deliverables
 How To Create WBS?
• Gather Critical Documents
– Gather critical project documents.

– Identify content containing project deliverables, such as the Project

Charter, Project Brief, Scope Statement and Project Management Plan,
etc.

• Identify Key Team Members

• Define Major Deliverables
• Decompose (Breakdown) Deliverables
 How To Create WBS?
• Gather Critical Documents
• Identify Key Team Members
– Identify the appropriate project team members.

– Analyze the documents and identify the deliverables.

• Define Major Deliverables

• Decompose (Breakdown) Deliverables
 How To Create WBS?
• Gather Critical Documents
• Identify Key Team Members
• Define Major Deliverables
– These are Level 1 deliverables that provide high-level summary of the
deliverable that must be met to satisfy the project scope.

– Verify 100% of scope is captured. This requirement is commonly

referred to as the 100% Rule.

• Decompose (Breakdown) Deliverables

 How To Create WBS?
• Gather Critical Documents
• Identify Key Team Members
• Define Major Deliverables
• Decompose (Breakdown) Deliverables
– Begin the process of breaking the Level 1 deliverables into unique
lower-Level deliverables.

– Continue breaking down the work until it can be assigned to the team
to complete - applying the 100% rule at each level.

– Ensure that all deliverables are mutually exclusive.

 WBS Levels
Decomposition is a method used for dividing and subdividing
the project scope and project deliverables into smaller, more
manageable parts.
• Level 0: Project Title or Final Deliverable

• Level 1: Major Deliverables

• Level 2…(N-1): Deliverables that can still be broken down

• Level N (Last Level): Can be assigned to the team to complete the last
level deliverables also known as “Work Packages”.
 WBS Levels
Level 0
Level 1

Level 2

Level 3

Work Package Work Package Work Package

@ Level 3 @ Level 4 @ Level 2
 Important Rules
• Use Nouns, Not Verbs

• 100% Rule

• Keep All Elements Mutually Exclusive

 Important Rules
• Use Nouns, Not Verbs
• 100% Rule
• Keep All Elements Mutually Exclusive
 Important Rules
• Use Nouns, Not Verbs
• 100% Rule
• Keep All Elements Mutually Exclusive
 WBS Formats
• The format of your WBS will depend on your team’s
or stakeholders’ preferences.
– Tree
– Outline
– Tabular
– Hierarchical
 WBS Formats
• Tree
• Outline
• Tabular
• Hierarchical
 WBS Formats
• Tree
• Outline
• Tabular
• Hierarchical
 WBS Formats
1. Software System
• Tree 1.1 Web
1.1.1 Web Site
• Outline 1.1.2 Database
1.1.3 Web Application
• Tabular 1.1.3.1 Admin Module
1.1.3.2 User Module
• Hierarchical
1.2 Mobile App
1.3 Manuals
1.3.1 User Manual
1.3.2 System Manual
2. Project Management
2.1 Status Report
2.2 Project Team
2.2.1 Full Time
2.2.2 Part Time
 WBS Formats
1. Software System
• Tree 1.1 Web
1.1.1 Web Site
• Outline 1.1.2 Database
1.1.3 Web Application
• Tabular 1.1.3.1 Admin Module
1.1.3.2 User Module
• Hierarchical
1.2 Mobile App
1.3 Manuals
1.3.1 User Manual
1.3.2 System Manual
2. Project Management
2.1 Status Report
2.2 Project Team
2.2.1 Full Time
2.2.2 Part Time
 WBS Formats
Level 1 Level 2 Level 3 Level 4

• Tree 1. Software System 1.1 Web 1.1.1 Web Site

1.1.2 Database
• Outline
1.1.3 Web 1.1.3.1 Admin
Application Module
• Tabular 1.1.3.2 User Module

1.2 Mobile App

• Hierarchical
1.3 Manuals 1.3.1 User Manual

1.3.2 System Manual

2. Project 2.1 Status Report

Management
2.2 Project Team 2.2.1 Full Time

2.2.2 Part Time

 WBS Formats
Level 1 Level 2 Level 3 Level 4

• Tree 1. Software System 1.1 Web 1.1.1 Web Site

1.1.2 Database
• Outline
1.1.3 Web 1.1.3.1 Admin
Application Module
• Tabular 1.1.3.2 User Module

1.2 Mobile App

• Hierarchical
1.3 Manuals 1.3.1 User Manual

1.3.2 System Manual

2. Project 2.1 Status Report

Management
2.2 Project Team 2.2.1 Full Time

2.2.2 Part Time

 WBS Formats
Level WBS Code Deliverable

• Tree 1 1 Software System

2 1.1 Web

• Outline 3
3
1.1.1
1.1.2
Web Site
Database
3 1.1.3 Web Application
• Tabular 4 1.1.3.1 Admin Module
4 1.1.3.2 User Module
• Hierarchical 2 1.2 Mobile App
2 1.3 Manuals
3 1.3.1 User Manual
3 1.3.2 System Manual
1 2 Project Management
2 2.1 Status Report
2 2.2 Project Team
3 2.2.1 Full Time
3 2.2.2 Part Time
 WBS Formats
Level WBS Code Deliverable

• Tree 1 1 Software System

2 1.1 Web

• Outline 3
3
1.1.1
1.1.2
Web Site
Database
3 1.1.3 Web Application
• Tabular 4 1.1.3.1 Admin Module
4 1.1.3.2 User Module
• Hierarchical 2 1.2 Mobile App
2 1.3 Manuals
3 1.3.1 User Manual
3 1.3.2 System Manual
1 2 Project Management
2 2.1 Status Report
2 2.2 Project Team
3 2.2.1 Full Time
3 2.2.2 Part Time
 Why Create WBS?
• Activity Definition

• Cost Estimating & Budgeting

• Resource Planning

• Risk Management Planning

 Related Performance Domains
Models, Methods, and Artifacts Performance Domain

Measurement
Dev Approach
and Life Cycle

Project Work
Stakeholders

Uncertainly
Planning

Delivery
Team
Type Title

Artifact Work Breakdown Structure (WBS)

 Summary
• Total Scope = Project Scope + Product Scope
• Work Breakdown Structure
• Deliverables Not Activities
• How To Create Work Breakdown Structure?
• Work Breakdown Structure Levels
• Important Rules
• Work Breakdown Structure Formats
• Why Create Work Breakdown Structure?
Q&A