Project Management Work Breakdown Structure Guide PDF
Project Management Work Breakdown Structure Guide PDF
Project Management Work Breakdown Structure Guide PDF
If you have any questions regarding this document or if you have a suggestion for
improvements, please contact:
E-mail vincent.f.granahan@tmr.qld.gov.au
Glossary........................................................................................................................ 4
1.0 Introduction....................................................................................................... 5
2.0 What is a Project?............................................................................................. 6
3.0 What is Project Management? ......................................................................... 6
4.0 What is a Work Breakdown Structure (WBS)?................................................ 7
5.0 Project Management WBS (PM WBS) .............................................................. 7
6.0 MR Standard Project Management WBS (PM WBS) ....................................... 7
7.0 Types of Projects .............................................................................................. 8
7.1 Road Infrastructure Projects........................................................................ 8
7.2 Business Improvement Projects.................................................................. 9
8.0 PM WBS Structure ............................................................................................ 9
9.0 Types of Standard PM WBS ........................................................................... 10
9.1 Standard PM WBS Template for Infrastructure Projects (Types 1, 2 & 3)10
9.1.1 PM WBS Levels Explained .................................................................................. 10
9.2 Standard PM WBS Template for Non Infrastructure Projects
(In Progress)........................................................................................................... 12
9.3 PM WBS Ownership.................................................................................... 13
9.4 PM WBS Revision/Update Process............................................................ 15
Attachment 1 - Project Governance Guidelines....................................................... 16
Attachment 2 Standard PM WBS for Infrastructure Projects CHART VIEW
(SUMMARY) ................................................................................................................ 20
Attachment 3 Standard PM WBS Template for Infrastructure Projects (WBS
Levels)......................................................................................................................... 22
Attachment 4 Standard PM WBS Template for Infrastructure Projects (WBS Levels
with Suggested Activities/Triggers).......................................................................... 28
Attachment 5 Standard PM WBS Template for Infrastructure Projects (with
Descriptions and Guidance) ...................................................................................... 40
Type 1 Significant road /infrastructure project that is complex, high risk or expensive
project and thus requires higher amounts of rigour and control.
Type 2 Relatively straightforward, low risk, road /infrastructure project for which a
project lesser amount of rigour and control is appropriate.
Type 3 Small, simple road /infrastructure project of low cost that progress quickly
project through the concept phase.
SIIP Project
Central responsibility for the delivery of the required improvements to
Projman, Works Management System, Roads Implementation Program
Application and the various databases that make up the Contract
Management System
PM WBS is mapped across these core business systems
Sets up business rules for use of the systems
OSF Project
Department of Transport and Main Roads
Delivery of a shared SAP solution for non-finance and HR functionality (i.e.
Program and Project Management). The OSF project is currently in
'Blueprint' phase which involves mapping existing business processes to
determine functionality requirements for a potential solution.
Complexity
In assessing the level of complexity (Low, Medium or High), give consideration to:
the type of project in terms of the construction environment, e.g. Urban and/or High
traffic volumes, Built-up areas and/or
significant traffic volumes, Rural and/or Low traffic volumes
the number and nature of stakeholders
how "routine" the project is
the number of related projects
can the project be delivered using the standard processes
number of different cost centres and agencies involved
the size location and composition of the project team
the likely use of unproven or unfamiliar technology
Type 1 Projects
The following characteristics are typical of type 1 projects:
funding of the Concept Phase would most likely be through the RIP
the project team may include personnel from other Main Roads organisations
the project manager should have few, if any, other responsibilities
will often have a Project Board or Steering Committee
should use templates: R1001, R1002, R1003, R2001, R4001, R4002
project reviews likely to be coordinated by the Major Projects Office
should have regular formal reporting requirements
Type 2 Projects
The following characteristics are typical of type 2 projects:
funding of the Concept Phase can be either through the RIP or Districts allocations
the project team usually fairly small and unlikely to include non-district staff
the project manager is likely to have other projects and responsibilities
may have a steering committee
should use templates R1001, R1004, R2002, R4003
reporting requirements vary but likely to be regular but less formal
Department of Transport and Main Roads
project reviews likely to be coordinated by Program Development & Delivery (PD&D)
Type 3 Projects
The following characteristics are typical of type 3 projects:
funding of the Concept Phase would most likely be through District allocations
usually do not require an options analysis
project team usually only one person the project manager
the project manager would normally have other projects and responsibilities
would not normally have a steering committee
should use templates R1001, R1005, R2003, R4003
informal "by exception" reporting is common
project reviews likely to be coordinated by the District Office
Signs
Provision for Traffic and Sidetracks
Obtain Approval for Preliminary Works The project manager needs to discuss the
necessary preliminary works to be undertaken
(what they are, extent of the work, etc.) for the
delivery of the project with the customer and
sponsor of the project. The customer and
sponsor approve the Preliminary Works
Acquire Right of Way A more detailed assessment of utility services
relocation requirements must be undertaken at
the preliminary design stage. ROW acquisitions
occur during the preparation of the detailed
design to ensure the project will be constructed
during the RIP timeframe.
Native Title Defining the area for Native Title evaluation must
ensure that all land that may be affected by the
project is identified.
The completed land acquisition must:
- provide adequate land for construction of the
project;
- modify existing access limitation to meet the
proposed arrangements; and
- reflects policy
Access Limitation must::
- provide Main Roads with adequate access
control over the road.
The Native Title Contact Officer can provide
advice on Native Title assessment and
information on the Native Title Work Procedures.
Finalisation Phase Project Management This phase covers the activities necessary to
produce, test and commission project
deliverables in accordance with the project plan.
Key activities in this phase include: managing the
construction contract, issue of the Practical
Completion Certificate and the official opening.
The Community Engagement Planner should be
updated and the project plan reviewed for this
phase.
Includes time spent on project meetings,
management of time (e.g. project scheduler),
cost and quality, and updating the Project
Plan/Community Engagement Planer.
Finalisation Phase Project Management Activities include project meetings, scheduler's
(General) time, cost and quality management work.
Project Plan - Finalisation Phase Includes updating, monitoring and managing the
Project Plan, engagement and communication,
managing project changes, controlling and
reporting progress, any revision/updating/re-
submission.
Defects Liability Period The Defect Liability Period commences on the
date of Practical Completion. It is the
responsibility of the contractor to repair defects,
which are attributable to the faults of the
contractor, which occur within a specified period
after the practical completion of works.
Final Certificate The Final Certificate is issued within 14 days
after receipt of the contractors Final Statement
(sets out the details of all claims made by the
Contractor which have not been settled or
otherwise resolved). In the certificate, the final
amount due to the Principal to the Contractor and
vice-versa is certified.
Community Engagement - Finalisation In this phase, it is important to engage customer
Phase and stakeholder to ensure that all their concerns
are identified and addressed. This is also the last
practical opportunity for the customers to voice
their views.
Complete Project Handover Report Includes confirmation of project completion,
receipt of documentation, maintenance
arrangements and the actual preparation of the
handover report.
It also includes the preparation of the
Consultant/Contractor Performance Final Report,
which must be completed within 2 weeks of
completion of any resulting infrastructure. The