Summary of Work Breakdown Structure and Project Lifecycle
Work Breakdown Structure (WBS) & Project Lifecycle Explained
Introduction
Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into manageable sections of work. It organizes project scope into deliverable-oriented components so teams can plan, estimate, assign, and control work effectively. This guide explains WBS concepts, demonstrates a standard WBS (Version 1.0), and gives examples and applications for independent study.
A Work Breakdown Structure (WBS) is a deliverable-oriented hierarchical decomposition of the work required to accomplish project objectives and create the required deliverables.
Why use a WBS?
- Clarifies project scope and boundaries
- Breaks complex projects into manageable chunks
- Improves cost and schedule estimating
- Helps assign responsibilities and track progress
Basic concepts
Hierarchy and decomposition
- A WBS is structured in levels. Level 1 is the overall project. Lower levels decompose that work into more detailed elements. The symbol "= Decomposes to lower level WBS elements" in diagrams signals this.
- Each element should represent a deliverable or a discrete scope of work.
WBS element naming and numbering
- Elements are typically numbered (e.g., 1.0, 2.0, 3.0) to show their position in the hierarchy.
- Sub-elements extend the numbering (e.g., 3.1, 3.1.1).
Good WBS practice: each lowest-level element (work package) should be small enough to estimate, schedule, and manage.
Standard WBS Version 1.0 — Overview
This standard WBS divides work into six major elements (level 1). Each major element contains sub-elements (level 2 and deeper) describing typical project activities.
Level 1 elements
- 1.0 Mission Analysis
- 2.0 Investment Analysis
- 3.0 Solution Development
- 4.0 Implementation
- 5.0 In-Service Management
- 6.0 Disposition
Detailed breakdown (selected highlights)
1.0 Mission Analysis
- 1.1 Identify Projected Demand for Services
- 1.2 Identify Technological Opportunities
- 1.3 Identify Projected Supply of Services
- 1.4 Mission Needs Analysis and Assessment
2.0 Investment Analysis
- 2.1 Requirements Definition
- 2.1.1 Initial Requirements Definition
- 2.1.2 Finalize Requirements
- 2.2 Alternatives Identification and Analysis
- 2.2.1 Alternatives Identification
- 2.2.2 Alternatives Analysis
3.0 Solution Development
Major sub-areas include program management, system engineering, design & production, facilities, test & evaluation, documentation, and support.
3.1 Program Management
- 3.1.1 Work Planning, Authorization and Management
- 3.1.2 Program Control
- 3.1.3 Contract Management
3.2 System Engineering
- 3.2.1 System Requirements and Definition
- 3.2.2 Analysis, Design, and Integration
- 3.2.3 Value Engineering
- 3.2.4 Supportability, Maintainability, and Reliability Engineering
- 3.2.5 Quality Assurance Program
- 3.2.6 Configuration Management
- 3.2.7 Human Factors
- 3.2.8 Security
3.3 HW/SW Design, Development and Production
- 3.3.1 Hardware Design and Development
- 3.3.2 Software Design and Development
- 3.3.3 HW/SW Integration, Assembly, Test and Checkout
- 3.3.4 Production Engineering
- 3.3.5 Production
3.4 Facilities and Physical Infrastructure Design and Development
- 3.4.1 Facility Planning and Design
- 3.4.2 Real Estate
- 3.4.3 Physical Infrastructure
3.5 Test and Evaluation
- 3.5.1 System Development Test and Evaluation
- 3.5.2 System Operational Test and Evaluation
- 3.5.3 System Independent Software Verification and Validation
- 3.5.4 Site Acceptance Testing
- 3.5.5 Independent Operational Test and Evaluation
3.6 Documentation (typical activities: creation, review, approval, distribution)
3.7 Support (logistics and readiness)
- 3.7.1 Logistics Support Planning
- 3.7.2 Test and Measurement Equipment Acquisition
- 3.7.3 Support and Handling Equipment Acquisition
- 3.7.4 Support Facilities Const
Sign up for the full summaryAlready have an account? Sign in
WBS Core Framework
Klíčová slova: Work Breakdown Structure (WBS)
Klíčové pojmy: WBS is a deliverable-oriented hierarchical decomposition, Stop decomposing when work packages are manageable for estimating and control, Use noun-based labels for WBS elements, Number WBS elements consistently (e.g., 3.1.2), Map WBS to schedule and budget for planning, Assign a single responsible owner to each work package, Standard WBS Level 1: Mission, Investment, Solution, Implementation, In-Service, Disposition, Include test & evaluation and support in Solution Development, Use WBS to improve comparison and benchmarking across projects, Review WBS for completeness, measurability, and consistent hierarchy