Work Breakdown Structure (WBS) Template

High Tech Consultant Ltd

Sport-four

Web-based Booking System Development Project Work Breakdown Structure (WBS)

Team Name: Group 1

Detail of group members:
1. Lai Ka Shun, Carson M00477530
2. Au Wai Nok M00477494
3. Kwok Tak Chor M00477566
4. Lam Ching Man, Vicky M00477533
5. Law Kit Hang, Leo M00477536
6. Leung Kim Fung, Ken M00477556
7. Wong Shu Fun, M00477576

Version 1.0

Prepared By High Tech Consultant Ltd.

December 8, 2018

Table of Contents

Introduction

Scope Management Approach

Scope Definition

Project Scope Statement

Work Breakdown Structure

Scope Verification

Scope Control

Sponsor Acceptance

Introduction

The Work Breakdown Structure (WBS) presented here lists all the work required to complete this project.

Outline View

1. Web-based Book System Development

1.1 Initiation

1.1.1 Develop Project Proposal

1.1.2 Submit Project Proposal

1.1.3 Project Proposal Signed by Sponsor

1.2 Planning

1.2.1 Determine Project Team

1.2.2 Project Team Kickoff Meeting

1.2.3 Develop Scope Management Plan

1.2.4 Develop Project Plan

1.2.5 Submit Scope Management Plan and Project Plan

1.2.6 Milestone: Project Plan Approved

1.3 Execution

1.3.1 Project Kickoff Meeting

1.3.2 Collect & Finalize User Requirements

1.3.3 Core Booking Function

1.3.3.1 Collect & Finalize User Requirement

1.3.3.2 System Design

1.3.3.3 Development

1.3.3.4 Prototype 1 Complete

1.3.4 Advance Booking Function

1.3.4.1 Collect & Finalize User Requirement

1.3.4.2 System Design

1.3.4.3 Development

1.3.4.4 Prototype 2 Complete

1.3.5 Deployment to UAT environment

1.3.6 System Integration Test (SIT)

1.3.7 User Acceptance Test (UAT)

1.3.8 Prepare User Training Materials

1.3.9 User Training

1.3.10 Rollout Preparation

1.3.11 Go Live

1.4 Control

1.4.1 Project Management

1.4.2 Project Update Meetings

1.4.3 Risk Management

1.4.4 Update Project Management Plan

1.5 Closeout

1.5.1 Procurement Audit

1.5.2 Document Lessons Learnt

1.5.3 Update All Deliverables

1.5.4 Gain Formal Acceptance

1.5.5 Archive All Documentations

Hierarchical Structure

Level / WBS Code / Element Name
1 / 1 / Web-based Book System Development
2 / 1.1 / Initiation
3 / 1.1.1 / Develop Project Charter
3 / 1.1.2 / Submit Project Charter
3 / 1.1.3 / Project Charter Signed by Sponsor
2 / 1.2 / Planning
3 / 1.2.1 / Determine Project Team
3 / 1.2.2 / Project Team Kickoff Meeting
3 / 1.2.3 / Develop Scope Management Plan
3 / 1.2.4 / Develop Project Plan
3 / 1.2.5 / Submit Scope Management Plan and Project Plan
3 / 1.2.6 / Milestone: Project Plan Approved
2 / 1.3 / Execution
3 / 1.3.1 / Project Kickoff Meeting
3 / 1.3.2 / Collect & Finalize User Requirements
3 / 1.3.3 / Core Booking Function
4 / 1.3.3.1 / Collect & Finalize User Requirement
4 / 1.3.3.2 / System Design
4 / 1.3.3.3 / Development
4 / 1.3.3.4 / Prototype 1 Complete
3 / 1.3.4 / Advance Booking Function
4 / 1.3.4.1 / Collect & Finalize User Requirement
4 / 1.3.4.2 / System Design
4 / 1.3.4.3 / Development
4 / 1.3.4.4 / Prototype 2 Complete
3 / 1.3.5 / Deployment to UAT environment
3 / 1.3.6 / System Integration Test (SIT)
3 / 1.3.7 / User Acceptance Test (UAT)
2 / 1.3.8 / Prepare User Training Materials
3 / 1.3.9 / User Training
3 / 1.3.10 / Rollout Preparation
3 / 1.3.11 / Go Live
2 / 1.4 / Control
3 / 1.4.1 / Project Management
3 / 1.4.2 / Project Update Meetings
3 / 1.4.3 / Risk Management
3 / 1.4.4 / Update Project Management Plan
2 / 1.5 / Closeout
3 / 1.5.1 / Procurement Audit
3 / 1.5.2 / Document Lessons Learnt
3 / 1.5.3 / Update All Deliverables
3 / 1.5.4 / Gain Formal Acceptance
3 / 1.5.5 / Archive All Documentations

Tabular View

Level 1 / Level 2 / Level 3
1Web-based Book System Development / 1.1 Initiation / 1.1.1 Develop Project Charter
1.1.2 Submit Project Charter
1.1.3 Project Charter Signed by Sponsor
1.2 Planning / 1.2.1 Determine Project Team
1.2.2 Project Team Kickoff Meeting
1.2.3 Develop Scope Management Plan
1.2.4 Develop Project Plan
1.2.5 Submit Scope Management Plan and Project Plan
1.2.6 Milestone: Project Plan Approved
1.3 Execution / 1.3.1 Project Kickoff Meeting
1.3.2 Collect & Finalize User Requirements
1.3.3 Core Booking Function
1.3.3.1 Collect & Finalize User Requirements
1.3.3.2 System Design
1.3.3.3 Development
1.3.3.4 Prototype 1 Complete
1.3.4 Advance Booking Function
1.3.4.1 Collect & Finalize User Requirements
1.3.4.2 System Design
1.3.4.3 Development
1.3.4.4 Prototype 1 Complete
1.3.5 Deployment to UAT environment
1.3.6 System Integration Test (SIT)
1.3.7 User Acceptance Test (UAT)
1.3.8 Prepare User Training Materials
1.3.9 User Training
1.3.10 Rollout Preparation
1.3.11 Go Live
1.4 Control / 1.4.1 Project Management
1.4.2 Project Update Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
1.5 Closeout / 1.5.1 Procurement Audit
1.5.2 Document Lessons Learnt
1.5.3 Update All Deliverables
1.5.4 Gain Formal Acceptance
1.5.5 Archive All Documentations

Tree Structure View

WBS Dictionary
Level / WBS Code / Element Name / Definition / Resource Assignment
1 / 1 / Web-based Book System Development / All work to implement the Web-based Book System. / -
2 / 1.1 / Initiation / The work to start the project. / -
3 / 1.1.1 / Develop Project Proposal / Project Manager to develop the Project Proposal. / Project Manager
3 / 1.1.2 / Submit Project Proposal / Project Proposal is delivered to the Project Sponsor. / Project Manager
3 / 1.1.3 / Project Proposal Signed by Sponsor / The Project Sponsor signs the Project Proposal which authorizes the Project Manager to move to the Planning Process. / Project Sponsor
2 / 1.2 / Planning / The work for the planning process for the project. / -
3 / 1.2.1 / Determine Project Team / The Project Manager determines the project team and requests the necessary resources. / Project Manager
3 / 1.2.2 / Project Team Kickoff Meeting / A project kickoff meeting is organized to officially start the planning phase. / Project Manager, Project Team
3 / 1.2.3 / Develop Scope Management Plan / Scope Management Plan is developed by the Project Manager. / Project Manager
3 / 1.2.4 / Develop Project Plan / Project Plan is developed by the Project Team. / Project Team
3 / 1.2.5 / Submit Scope Management Plan and Project Plan / Project Manager submits the scope management plan and project plan for approval / Project Manager
3 / 1.2.6 / Project Management Plan Approved / The project management plan is approved and the Project Manager is authorized to proceed with the project according to the project management plan. / Project Sponsor
2 / 1.3 / Execution / The work for executing the project. / -
3 / 1.3.1 / Project Kickoff Meeting / Project Manager conducts a formal kick off meeting with the project team, project stakeholders and project sponsor. / Project Manager, Project Team, Project Stakeholders and Project Sponsor
3 / 1.3.2 / Collect & Finalize User Requirements / Initial requirements are collected from various stakeholders and uses and are reviewed. Clarification and balance the requirements between stakeholders are necessary between they can be finalized. / Project Manager, Project Team, Project Stakeholders
3 / 1.3.3 / Core Booking Function / Project Team delivery the core booking function based on 1st increment / Project Team
4 / 1.3.3.1 / Collect & Finalize User Requirement / Project Teams comes up with user requirement from project stakeholders / Project Team
Project Stakeholders
4 / 1.3.3.2 / System Design / Project Team comes up with web & system design based on user requirement / Project Team
4 / 1.3.3.3 / Development / The procurement and work on all hardware, software and facility needs for the project. / Project Team
4 / 1.3.3.4 / Prototype 1 Complete / All core booking function tested and all identified errors corrected / Project Manager, Project Team, Project Stakeholders
3 / 1.3.4 / Advance Booking Function / Project Team delivery the core booking function based on 2nd increment / Project Team
4 / 1.3.4.1 / Collect & Finalize User Requirement / Project Teams comes up with user requirement from project stakeholders / Project Team
Project Stakeholders
4 / 1.3.4.2 / System Design / Project Team comes up with web & system design based on user requirement / Project Team
4 / 1.3.4.3 / Development / The procurement and work on all hardware, software and facility needs for the project. / Project Team
4 / 1.3.4.4 / Prototype 2 Complete / All advance booking function tested and all identified errors corrected / Project Manager, Project Team, Project Stakeholders
3 / 1.3.5 / Deployment to UAT environment / Installs the new system for testing and customizations of user interfaces. / Project Team
3 / 1.3.6 / System Integration Test (SIT) / The technical resources integrate the new system with existing systems and carry out related tests. / Project Team
3 / 1.3.7 / User Acceptance Test (UAT) / The system is tested with a select set of users. / Project Team, Users
2 / 1.3.8 / Prepare User Training Materials / Training materials are prepared by the Project Team for user training purposes. / Project Team
3 / 1.3.9 / User Training / All users are provided with one day training class. Line managers are provided with an additional half day training to cover the reporting functions. / Project Team, all Users
3 / 1.3.10 / Rollout Preparation / The Project Team plans for the rollout of the project and do the necessary preparation work. / Project Team
3 / 1.3.11 / Go Live / System goes live with all users. / Project Team
2 / 1.4 / Control / The work involved for the control process of the project. / -
3 / 1.4.1 / Project Management / Overall project management for the project. / Project Manager
3 / 1.4.2 / Project Update Meetings / Project Manager conducts weekly project update meetings with the Project Team. / Project Manager, Project Team
3 / 1.4.3 / Risk Management / Risk management tasks are performed as defined in the Risk Management Plan. / Project Manager, Project Team
3 / 1.4.4 / Update Project Management Plan / Project Manager updates the Project Management Plan as the project progresses. / Project Manager
2 / 1.5 / Closeout / The work to close-out the project. / -
3 / 1.5.1 / Procurement Audit / An audit of all hardware and software procured for the project ensures that the all procured products are accounted for; records and invoices are kept in a proper manner. / Project Manager
3 / 1.5.2 / Document Lessons Learnt / Project Manager along with the project team performs a session to gather the lessons learnt and document them. / Project Manager, Project Team
3 / 1.5.3 / Update All Deliverables / All files and records are updated. / Project Manager, Project Team
3 / 1.5.4 / Gain Formal Acceptance / The Project Sponsor formally accepts the project by signing the acceptance document included in the project plan. / Project Manager, Project Sponsor
3 / 1.5.5 / Archive All Documentations / All project related files and documents are formally archived. / Project Manager

Glossary of terms

WBS Code:A unique identifier assigned to each element in a Work Breakdown Structure for the purpose of designating the elements hierarchical location within the WBS.

Work Package:A Work Package is a deliverable or work component at the lowest level of its WBS branch. It is estimated that between 8 to 80 hours of work is required to complete any Work Package within the WBS.

WBS Component:A component of a WBS which is located at any level. It can be either a Work Package or a WBS Element.

WBS Element:A WBS Element is a single WBS component and its associated attributes located anywhere within a WBS. A WBS Element can contain work, or it can contain other WBS Elements or Work Packages.

Page 1 of Pages 14