Work Breakdown Structures

Fifteen Project Management Job

Functions*
 Define scope of project  Identify and evaluate risks
 Identify stakeholders,  Prepare contingency plan
decision-makers, and
escalation procedures  Identify interdependencies
 Develop detailed task list  Identify and track critical
(work breakdown milestones
structures)  Participate in project phase
 Estimate time requirements review
 Develop initial project  Secure needed resources
management flow chart  Manage the change control
 Identify required resources process
and budget
 Report project status
 Evaluate project
requirements
Overlap of Process Groups in a Phase
(PMBOK® Guide, 2000)
Relationships Among Process Groups and
Knowledge Areas (PMBOK® Guide 2000, p. 38)
Relationships Among Process Groups and
Knowledge Areas (PMBOK® Guide)
 Project Planning

 The main purpose of project planning is to guide

execution
 Every knowledge area includes planning
information
 Key outputs include:
 A team contract
 A scope statement (project charter)
 A work breakdown structure (WBS)
 A project schedule, in the form of a Gantt chart with all
dependencies and resources entered
 A list of prioritized risks
PMI Process Project Gantt Chart
Scope Planning and the
Scope Statement

 A scope statement is a document used to

develop and confirm a common
understanding of the project scope. It
should include
 a project justification
 a brief description of the project’s products
 a summary of all project deliverables
 a statement of what determines project
success
Scope Planning and the Work
Breakdown Structure
 After completing scope planning, the next
step is to further define the work by
breaking it into manageable pieces
 Good scope definition
 helps improve the accuracy of time,
cost, and resource estimates
 defines a baseline for performance
measurement and project control
 aids in communicating clear work
responsibilities
List of Prioritized Risks