Lecture 2 – PMBOK + WBS

Project scope statement

Definition: Project scope is the part of project planning that involves determining and documenting a list
of specific project goals, deliverables, tasks, costs and deadlines

WBS: Work break down structure

PMBOK Process Group

The Process - Plan Do Check Act

 Initiating
o Define new project/phase, identify
stakeholders, obtain authorization
 Authorize the work
o Project Charter: the contract between the
project manager and the sponsor
o Stakeholder register: everybody participating or
affected by the project
 Planning
o Develop an integrated project management plan
to attain project objectives
o Project management plans + related documents
 Scope, requirements, schedule, cost, quality, HR, communication, risk,
procurement, change, stakeholders
 Executing
 Monitoring + Controlling
 Closing

Not too many projects

are completed ahead of
schedule and under
budget!
PM Processes Overlap

PMBOK Processes: project lifecycle

Project Planning

 Components of work that need to be completed to achieve the new capability – Work
Breakdown Structure
 Determining the precedence, dependence between activities-work components – Network
diagrams, Gantt Charts
 Identifying resources needed to complete: people, tools, sub-contractors
 Estimating time required, associated costs
 Creating a project plan

Project Scope Management (PMBOK framework)

 Scope planning inputs

o Charter and environment analysis
o Organization process
o Scope planning
 Scope definition
o Stakeholder analysis
o Translating product objectives
o Identify alternatives
o Success criteria
o Quality: user experience, etc

Scope Planning Outputs

- Project Scope Statement

 Objectives
 Scope definition
 Requirements (functional, non-functional, performance, security, integration)
 Project boundaries
 Deliverables
 Acceptance criteria
 Assumptions and constraints
- Work breakdown structure – key output of scope planning
- Scope Verification
 Inspection
 Acceptance
 Accepted changes
- Scope Control
WBS – Work Breakdown Structure

Objective of WBS:

 Subdividing the project into pieces of work or work packages that will produce either
intermediate or final deliverables
 Number of levels will depend upon size, complexity of project – as example:
 Level 1 – Project
 Level 2 – Sub-project
 Level 3 – Work package
 Level 4 – Activity

WBS Example – Building a house

 Level 1: House
 Level 2:
o Purchase land
o Excavation & Foundation
o Frame
o Walls & Ceilings & windows
o Interior systems
 Level 3 – Interior systems:
o electrical,
o plumbing,
o Doors & trim
o HVAC
 Level 4: HVAC
o Ducts,
o Furnace

WBS Work Package

- Activity to be done
- Resource requirements
- Estimated time to perform activity
- Costs for the activity: internal, external
- Responsibilities: for execution, for inspection, for approval – Responsibility matrix to recap
- Specific outcomes & deliverables for the task
- Preconditions before activity can be initiated
- QA process
 - Risks

WBS: Responsibility Matrix