Project Management Implementation
Hot Topic Training 
to help you get things done
on time, within budget, within scope, with acceptable quality levels
Hot Topic Training
Business Case / Scope
Work Breakdown Structure
Project Effort Estimating & Cost Risk Management Status Reporting
NYS OFT Project Management Implementation 2
Project Management Lifecycle: Initiation
Origination Initiation Planning Execution and Control
Conduct Phase Kick-off
Closeout
Develop Project Proposal
Prepare for the Project
Conduct Planning Kick-off
Conduct PostImplementation Review
Define CSSQ
Refine CSSQ
Manage CSSQ
Evaluate Project Proposal
Perform Risk Identification
Perform Risk Assessment
Monitor and Control Risks
Perform Administrative Closeout
Develop Initial Project Plan
Refine Project Plan
Manage Project Execution
Select Projects
Confirm Approval to Proceed
Confirm Approval to Proceed
Gain Project Acceptance
NYS OFT Project Management Implementation
Work Breakdown Structure (WBS)
What is it ?  what it is not! Why do I need to do this ? Okay, how do I do this ?
NYS OFT Project Management Implementation 4
Work Breakdown Structure (WBS)
What is it ? Defined: A grouping of project elements or components which defines the total project scope. A WBS is deliverable-oriented and each descending level represents an increasingly detailed definition of a component.
NYS Project Management Guidebook
NYS OFT Project Management Implementation
System Development Lifecycle
Work Breakdown Structure
System Initiation
Established Initiation Environment
System Requirements Analysis
Established Requirements Analysis Environment Business Requirements
System Design
System Construction
Established Construction Environment
System Acceptance
Established Acceptance Environment Data Initialization and Conversion Test Results Acceptance Test Results
System Implementation
Established Implementation Environment Deployed and Operational System Transitioned Support Responsibilities
Established Design Environment
Proposed Solution
Technical Architecture
Refined System Standards
System Schedule
Business Process Model
System Standards
Coded Software Modules
Logical Data Model
Physical Database
Unit, Integration and System Test Results User and Training Materials
Updated Supporting Materials
Functional Specification
System Component Prototypes
Technical Specifications
Technical Documentation
Project Management Lifecycle NYS OFT Project Management Implementation
PM Life cycle to SDLC
Project Management Lifecycle
Project Origination Project Initiation Project Planning Project Execution and Control Project Closeout
System Initiation
System Requirements Analysis
System Design
System Construction
System Acceptance
System Implementation
System Development Lifecycle
NYS OFT Project Management Implementation
Work Breakdown Structure (WBS)
What it is not! Not a project schedule !! Not calendar based No resources applied No level of effort No dependencies Not a static document
NYS OFT Project Management Implementation
Work Breakdown Structure (WBS)
Is based on scope statement Provides means for defining total scope of work Depicts hierarchical listing of deliverables and activities Includes project management as well as product deliverables Describes industry standard product lifecycles
NYS OFT Project Management Implementation 9
Work Breakdown Structure (WBS)
Simply stated, it is an organized list of decomposed activities (tasks) to be done. A growing to-do list !
NYS OFT Project Management Implementation
10
Work Breakdown Structure (WBS)
Why do I need to do this ?
High level to detail level, objective view of amount of work to do Ensures all work needed is included Ensures unnecessary work is excluded Serves as an efficient tool to build consensus
NYS OFT Project Management Implementation 11
Work Breakdown Structure (WBS)
Why else?
Identifies deliverables and activities Understand amount of resources needed, from a roles perspective Understand relationship dependencies within the WBS only Foundation for estimate
NYS OFT Project Management Implementation
12
Work Breakdown Structure (WBS)
More reasons why  Becomes input to:
Activity definition Resource planning Cost estimating Risk Management planning
NYS OFT Project Management Implementation 13
Work Breakdown Structure (WBS)
How do I do this ? Where is the Proposed Project Business Case and Project Scope Statement?
Proposed Project Business Case Project Scope Statement
Work Breakdown Structure
NYS OFT Project Management Implementation
14
Work Breakdown Structure (WBS)
How do I do this? Start at the top --- work to the bottom
Highest level  major area Break down the major area components Lowest level  manageable work to be done
NYS OFT Project Management Implementation
15
Work Breakdown Structure (WBS)
Tips:
Use project team Use templates Use anyone who has done this before Lowest component is real work done by real person in approximately 2 weeks time Include everything (product and project items)! Iterative process  do it again!
NYS OFT Project Management Implementation
16
The Work Breakdown Structure
Level 1
Project Highest level of the WBS  may reference other projects if part of a larger program Discrete products or services that, when combined, meet the objectives of the project Component deliverables that in their totality form deliverables. Low-level deliverable that may be assigned to another project manager to plan and execute. Forms the body of the schedule, however some activities may be found in the WBS.
Level 2
Deliverable
Level 3
Sub Deliverable
Level 4
Work package
Level 5
Activities
NYS OFT Project Management Implementation
17
The Work Breakdown Structure
Level 1
Project Project
Level 2
Deliverable
Level 3
Sub Deliverable 1.1 1.2 2.1
Level 4
Work package
Level 5
Activities
1.1.1
1.1.2
1.1.3
1.1.2.1 Project Management Implementation 1.1.2.2 1.1.2.3 NYS OFT
1.1.2.4
18
Work Breakdown Structure (WBS)
Formats:
Major Component Sub component 1 Activity 1.1 Activity 1.2
Indented List 
Sub component 2 Activity 2.1 Task 2.1.1 Sub task 2.1.1.1 Sub component 3 Sub component 4
NYS OFT Project Management Implementation
19
Work Breakdown Structure (WBS)
Project: What is to be accomplished? Deliverables & Tasks: What needs to be done to support the above? Summary Task: <noun describing deliverable> Ex., List of Requirements Detail Tasks: <present tense verb> Ex., Interview Users Milestone: <deliverable> <past tense verb> Ex., List of Requirements Completed Dependencies: In what order? Duration / work: How long will it take? Resource / Assignments: Who (Roles) is going to do it?
NYS OFT Project Management Implementation 20
Work Breakdown Structure (WBS)
1. List of Requirements SUMMARY 1.1 Gather requirements DETAIL 1.1.1 Interview Users DETAIL 1.1.2 Review current system 1.1.3 Review current legislation 1.1.4 Review pending legislation 1.1.5 Enter requirements into requirements tracking system 1.1.6 Requirements Gathered MILESTONE 1.2 Gain approval of Requirements DETAIL 1.2.1 Present complete requirement documentation to users for sign off DETAIL 1.2.2 Update documentation as per reviewers requests 1.2.3 Approval of Requirements received MILESTONE 1.3 List of Requirements Completed MILESTONE
NYS OFT Project Management Implementation 21
Work Breakdown Structure (WBS)
1. Hot Topic Training SUMMARY 1.1 Determine needs DETAIL 1.2 Design training DETAIL 1.2.1 Develop WBS Presentation (TASK) 1.2.2 Develop Risk Presentation (TASK) 1.3 Deliver training DETAIL 1.3.1 Present WBS training (TASK) 1.4 Evaluate training DETAIL 1.5 User Training completed MILESTONE
NYS OFT Project Management Implementation
22
Work Breakdown Structure (WBS)
1. Hot Topic Training SUMMARY 1.1 Determine needs DETAIL 1.2 Design training DETAIL 1.2.1 Develop WBS Presentation (TASK) 1.2.1.1 Scan available information for use 1.2.1.2 Build PowerPoint slides (ACTIVITY) 1.2.1.3 Generate instructor scripts 1.2.1.4 Generate examples 1.2.1.5 Review and Revise with PMO 1.2.1.6 WBS Presentation approved (MILESTONE) 1.2.2 Develop RISK Presentation (TASK)
NYS OFT Project Management Implementation
23
Work Breakdown Structure (WBS)
The Scope and WBS evolve together as the project is more clearly defined The WBS can be documented to a low level for certain deliverables early in the process. Many deliverables will not have as much detail initially. The scope and WBS are team efforts  use the project team as much as possible!
NYS OFT Project Management Implementation 24
Work Breakdown Structure (WBS)
100 Percent. The deliverables should cover the
entire scope of the project.
Current. The WBS should reflect current
information known about the project.
Progressive. The WBS is iterative and should
illustrate a progression of detail over time.
Review. WBS against Guidelines and Checklist
for high-quality deliverable.
NYS OFT Project Management Implementation
25
Work Breakdown Structure (WBS)
Sad Fact  The very dynamic WBS
AIX / ESA
NYS OFT Project Management Implementation
26
WBS Across the PM Lifecycle
Origination
Proposed Project Business Case and Project Solution describes the work Nature of the work suggests WBS contents High-level deliverables defined Detailed deliverables may be identified Work packages defined Project lifecycle fully integrated Scope managed Change control occurs
NYS OFT Project Management Implementation 27
Initiation
Planning
Execution and Control
Work Breakdown Structure (WBS)
Summary:
Refinement of Business Case and Scope Provides big picture view Manageable tasks Measurable work Foundation for additional efforts
NYS OFT Project Management Implementation
28
Work Breakdown Structure (WBS)
Summary:
WBS defines the What of the project . the project schedule defines the When and often the Who.
PMI Practice Standard for Work Breakdown, 2001
Scope, WBS, and other pieces evolve as more information becomes known. Review often!
NYS OFT Project Management Implementation
29
References:
NYS Project Management Guidebook http://www.oft.state.ny.us/pmmp/pmo.htm
If you need help or just have a question ..
PMO Contacts:
Brenda Breslin, 474-5171 Terry Remillard, 474-4534 Jim Madigan, 473-3288 Drew Prescott, 408-2874
NYS OFT Project Management Implementation 30
Work Breakdown Structure (WBS)
NYS OFT Project Management Implementation
31