Professional Documents
Culture Documents
Chapter 6 & 7
Eric Verzuh
Detailed Planning Model
From project definition
PROJECT PLAN
Project rules PLANNING Scope and deliverables All project tasks
Schedule
Responsibilities
PREPLANNING
STEP 1 Budget
Development approach Develop a work Resource forecast
Risk management
Risk management tasks breakdown structure
CHAPTER 5
CHAPTER 6
PROJECT
PLAN
Work Breakdown Structure (WBS)
The work breakdown structure (WBS) is the tool for
breaking down a project into its component parts -
identifies all the manageable tasks in a project.
It is the foundation of project planning and a most
important technique used in project management.
The WBS uses outputs from project definition and
risk management.
It is important to view the project at high level (to
balance cost-schedule-quality equilibrium) as well as
to understand the whole project in terms of its parts.
Purpose of WBS
Building a WBS helps to:
Provide a detailed illustration of project scope.
Monitor progress each task in WBS is a measurable
unit or work
Create accurate cost and schedule estimates
Build project teams defining work assignments
Building a WBS
There are two types of tasks or activities on a WBS
summary tasks summarizes several subordinate tasks
work packages each of the separate tasks
Accomplishing summary tasks by performing all the simple
work packages
2.2.1 2.2.2 2.2.3 2.2.4 2.3.1 2.3.2 2.3.3 3.2.1 3.2.2 3.2.3 3.2.4
Identify Dig Install Cover Remove Prepare Plant Mark Install Install Paint/
sprinkler trenches pipe and sprinkler debris soil lawn fence line posts fencing stain
locations hardware system seed and posts and gates fence
Work breakdown structure as outline form
Home landscape project
1.0 Design home landscape Work packages
2.0 Put in lawn
2.1 Acquire lawn materials
2.2 Install sprinkler system
2.2.1 Identify sprinkler locations
2.2.2 Dig trenches
2.2.3 Install pipe and hardware
2.2.4 Cover sprinkler system
2.3 Plant grass
2.3.1 Remove debris Summary tasks
2.3.2 Prepare soil (fertilize, rake)
2.3.3 Plant lawn seed
2.4 Plant shrubs
3.0 Build fence
3.1 Acquire fence material
3.2 Construct the fence
3.2.1 Mark fence line and posts
3.2.2 Install posts
3.2.3 Install fencing and gates
3.2.4 Paint/ stain fence
WBS Step one: Begin at the Top
Breaks down a project into successively finer levels of
detail (use Statement of Work or Project Proposal)
Continues until all meaningful tasks or work packages
have been identified
1. Project
2. Major tasks in the project
3. Subtasks in the major tasks
4. Activities (or work packages) to be completed
WBS Step two: Name all the Tasks
Naming all the tasks breaking project into
manageable details is a difficult process
Essential to involve all the team members bringing in
diverse skills
Use participative planning
After breaking the project to the first two tiers, get the
expert teams to detail out each identified summary tasks
further into work packages.
Then use a core team to construct the entire WBS
WBS Step three: Organise the WBS
There is more than one way to organise tasks on a
project.
Different ways of organising work packages may
emphasize different aspects of a project. ex.
Emphasizing various components of a product, or phases in
production process.
The driving factor is the concerns of individual
stakeholders, communication, visibility and the
structure of work environment
Organising tasks on a Project
Widget Release 4.0 Project
Widget Release 4.0 Project 1.0 Define Release 4.0 requirements
1.0 Develop component M1B 1.1 Define M1B product requirements
1.1 Define M1B product requirements 1.2 Define R45 product requirements
1.2 Design M1B 2.0 Design Release 4.0
1.3 Build M1B 2.1 Design M1B
1.3.1 Upgrade M1B core modules 2.2 Design R45
1.3.2 Build new M1B modules 3.0 Build Release 4.0
1.3.3 Test and certify M1B 3.1 Upgrade core modules
2.0 Develop Component R45 3.1.1 Upgrade M1B core modules
2.1 Define R45 product requirements 3.1.2 Upgrade R45 core modules
2.2 Design R45 3.2 Build new modules
2.3 Build R45 3.2.1 Build new M1B modules
2.3.1 Upgrade R45 core modules 3.2.2 Build new R45 modules
2.3.2 Build new R45 modules 3.3 Test components
2.3.3 Test and certify R45 3.3.1 Test and certify M1B
3.0 Integrate and test Release 4.0 3.3.2 Test and certify R45
4.0 Integrate and test Release 4.0
Emphasize visibility
of the two main Emphasize visibility on
components the major phases of
the new release
Criteria for a successful WBS
An effective WBS is useful in planning, communicating
and tracking the project.
1. The WBS must be broken down starting at the top
Use standard project management software
Present meaningful project information at the summary
task level
2. Work packages must add up to the summary task
3. Each summary task and work package must be
named as an activity that produces the product
Avoiding open ended tasks and activities.
Break the project into small, meaningful, manageable units of work
Realistic Scheduling
Chapter 7
Eric Verzuh
A Realistic Schedule
a realistic scheduling tops the list for a successful
project.
Includes a detailed knowledge of the work to be
done
Has task sequences in the correct order
Accounts for external constraints beyond the control
of the team
Can be accomplished on time, given the availability
of skilled people and enough equipment (resources)
Detailed Planning Model
From project definition
STEP 1
PREPLANNING
Development approach Develop a work
Risk management
Risk management tasks breakdown structure
CHAPTER 5
CHAPTER 6
PROJECT
PLAN
Recap of the steps in planning
Preplanning activities:
Create the project definition
Develop a risk management strategy
Planning steps
1. Build a work breakdown structure
2. Identify task relationships
3. Estimate work packages
4. Calculate initial schedule
5. Assign and level resources
Planning Step two: Identify task
relationships
The sequence in which detailed tasks work packages
will be performed
Example - Home landscape project
Acquire lawn materials
Remove debris
Prepare soil
Plant lawn seed
Plant shrubs
What is the proper sequence?
Are there any sequence constraints? (certain tasks that must be
performed before others)
RESULT Predecessor table or Network diagram
Predecessor Table and Network Diagram
1 3 4
Start Finish
2 5
AON and AOA Network Diagram
1 3 4
Start Finish
2 5
3
AON Activity on Node
1
network diagram 4
2 5
0 T- 1 2 4 T- 3 8 8 T- 4 9
LS 2 LF LS 4 LF LS 1 LF
LS 4 LF LS 12 LF LS 0 LF
0 T- 1 2 4 T- 3 8 8 T- 4 9
9 2 11 11 4 15 15 1 16
0 4 4 4 12 16 16 0 16
0 T- 1 2 4 T- 3 8 8 T- 4 9
9 2 11 11 4 15 15 1 16
9 7 7
0 Start 0 (2 free float + 7 interfering float) (7 interfering float) (7 free float)
0 0 0
0 T- 2 4 4 T- 5 16
16 Finish 16
0 4 4 4 12 16 16 0 16
0 0
The Critical Path is Start T.2 T.5 Finish and duration is 16 days
Schedule Table
Task Task Name Dura EST EFT LST LFT Total Free Intg Predecessor
ID tion Float Float Float
1 Acquire lawn 2 0 2 9 11 9 2 7 -
materials
2 Remove 4 0 4 0 4 0 0 0 -
debris
3 Prepare soil 4 4 8 11 15 7 0 7 1, 2
4 Plant lawn 1 8 9 15 16 7 7 0 3
seeds
5 Plant shrubs 12 4 16 4 16 0 0 0 2
Critical Tasks are T.2 & T.5 with zero total float
Class Exercise-4
Determine the Critical Path and Project duration
Activity Description Duration Immediate
in weeks Predecessors
Time Period
Task ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
1
2
3
4
5
Class Exercise-5
Develop the Gantt Chart showing Early Start- Early Finish and
Late Start Late Finish for Class Exercise-4 after filling this table