PMdistilled ForumExample Category: PMdistilled forumWork Breakdown Structure - WBSPost Reply

Post Reply: Work Breakdown Structure - WBS

<blockquote><div class="quotetitle">Quote from <a class="profile-link highlight-admin" href="https://pmri.in/forum/profile/pmdistilled/">pmdistilled</a> on 30/08/2024, 6:23 PM</div>
<h6 class="wp-block-heading has-medium-font-size">Key points</h6>

<ul class="wp-block-list">
<li class="has-medium-font-size">The <a href="https://pmri.in/pbs/">Product Breakdown Structure (PBS)</a> is super imposed with the actual work that need to be done to construct them to arrive at the Work Breakdown Structure (WBS)</li>

<li class="has-medium-font-size">Once the WBS is defined and baselined, all further estimates will be based on it</li>

<li class="has-medium-font-size">WBS comprises of various levels. As the levels increases the detailing increases</li>

<li class="has-medium-font-size">The lowest level in a WBS are known as Work Packages</li>

<li class="has-medium-font-size">Work packages are chunks of work which can be completed between 8 and 80 hours of work. This is known as 8-80 rule</li>

<li class="has-medium-font-size">The entire scope of the project must be reflected in the WBS. This is known as 100 percent rule</li>

<li>If something is missed out in the WBS, it will not be there in the final product</li>

<li class="has-medium-font-size">Prior to schedule development, work packages are further decomposed into activities</li>
</ul>

Work Breakdown Structures are deliverable oriented grouping of work. A Work Breakdown Structure (WBS) is a hierarchical decomposition of the project scope into smaller, more manageable work packages. It organizes project work into hierarchical levels, making it easier to plan, manage, and track project activities. Work packages can be in the form of a tree or list.

WBS tree structure

<figure class="wp-block-image size-full"><a href="https://pmri.in/wp-content/uploads/2024/04/wbs-tree-structure.png"><img src="https://pmri.in/wp-content/uploads/2024/04/wbs-tree-structure.png" alt="" class="wp-image-1173"/></a></figure>

WBS List structure

<figure class="wp-block-image size-full"><a href="https://pmri.in/wp-content/uploads/2024/04/wbs-list-structure.png"><img src="https://pmri.in/wp-content/uploads/2024/04/wbs-list-structure.png" alt="" class="wp-image-1174"/></a></figure>

Here are examples of Work Breakdown Structures for both Engineering, Procurement, and Construction (EPC) projects and Information Technology (IT) projects:

<h5 class="wp-block-heading has-medium-font-size">Example 1: Work Breakdown Structure for an EPC Project (Construction of a Power Plant)</h5>

<ol class="wp-block-list">
<li class="has-medium-font-size">Project Management
<ul class="wp-block-list">
<li>Project Planning</li>

<li>Project Coordination</li>

<li>Reporting and Communication</li>
</ul>
</li>

<li class="has-medium-font-size">Engineering
<ul class="wp-block-list">
<li>Site Survey and Assessment</li>

<li>Conceptual Design</li>

<li>Detailed Engineering</li>

<li>Permitting and Approvals</li>
</ul>
</li>

<li class="has-medium-font-size">Procurement
<ul class="wp-block-list">
<li>Material Procurement</li>

<li>Equipment Procurement</li>

<li>Vendor Management</li>
</ul>
</li>

<li class="has-medium-font-size">Construction
<ul class="wp-block-list">
<li>Site Preparation</li>

<li>Foundation Construction</li>

<li>Structural Steel Erection</li>

<li>Installation of Equipment</li>

<li>Electrical and Instrumentation Work</li>

<li>Mechanical Installation</li>

<li>Piping and Plumbing</li>
</ul>
</li>

<li class="has-medium-font-size">Commissioning and Testing
<ul class="wp-block-list">
<li>Pre-commissioning Activities</li>

<li>Functional Testing</li>

<li>Performance Testing</li>

<li>System Integration Testing</li>
</ul>
</li>

<li class="has-medium-font-size">Quality Assurance and Control
<ul class="wp-block-list">
<li>Inspection and Testing</li>

<li>Quality Audits</li>

<li>Compliance Verification</li>
</ul>
</li>

<li class="has-medium-font-size">Health, Safety, and Environmental (HSE)
<ul class="wp-block-list">
<li>Safety Planning and Training</li>

<li>Hazard Identification and Mitigation</li>

<li>Environmental Compliance</li>
</ul>
</li>

<li class="has-medium-font-size">Project Closeout
<ul class="wp-block-list">
<li>Punch List Completion</li>

<li>Documentation and Handover</li>

<li>Lessons Learned</li>
</ul>
</li>
</ol>

<h5 class="wp-block-heading has-medium-font-size">Example 2: Work Breakdown Structure for an IT Project (Development of a Software Application)</h5>

<li>Stakeholder Management</li>

<li>Risk Management</li>

<li>Reporting and Documentation</li>
</ul>
</li>

<li class="has-medium-font-size">Requirements Gathering
<ul class="wp-block-list">
<li>Stakeholder Interviews</li>

<li>User Surveys</li>

<li>Requirements Documentation</li>
</ul>
</li>

<li class="has-medium-font-size">Design
<ul class="wp-block-list">
<li>Architecture Design</li>

<li>User Interface Design</li>

<li>Database Design</li>
</ul>
</li>

<li class="has-medium-font-size">Development
<ul class="wp-block-list">
<li>Frontend Development</li>

<li>Backend Development</li>

<li>Database Development</li>
</ul>
</li>

<li class="has-medium-font-size">Testing
<ul class="wp-block-list">
<li>Unit Testing</li>

<li>Integration Testing</li>

<li>System Testing</li>

<li>User Acceptance Testing (UAT)</li>
</ul>
</li>

<li class="has-medium-font-size">Deployment
<ul class="wp-block-list">
<li>Deployment Planning</li>

<li>Installation and Configuration</li>

<li>Data Migration</li>
</ul>
</li>

<li class="has-medium-font-size">Training and User Support
<ul class="wp-block-list">
<li>User Training</li>

<li>Documentation Development</li>

<li>Help Desk Support</li>
</ul>
</li>

<li class="has-medium-font-size">Maintenance and Support
<ul class="wp-block-list">
<li>Bug Fixes and Updates</li>

<li>Performance Monitoring</li>

<li>User Feedback and Improvement</li>
</ul>
</li>
</ol>

In both examples, the Work Breakdown Structure breaks down the project scope into hierarchical levels, each representing a different aspect of the project. This hierarchical structure makes it easier to organize, plan, and manage project activities, ensuring that all necessary work is identified and accounted for.

<h5 class="wp-block-heading has-medium-font-size">100% rule</h5>

The 100% rule, also known as the "100% rule of allocation," is a fundamental principle in Work Breakdown Structure (WBS) development. It states that the sum of the work at the lowest level of the WBS must equal 100% of the work represented by the higher-level parent element. In other words, the WBS should fully decompose the project scope, and every component of the project should be included in the WBS without any gaps or overlaps.

Here's how the 100% rule works:

<ol class="wp-block-list">
<li class="has-medium-font-size">Hierarchy: The WBS is organized hierarchically, with higher-level elements representing major deliverables or phases of the project and lower-level elements representing progressively detailed tasks or work packages.</li>

<li class="has-medium-font-size">Decomposition: Each higher-level element in the WBS is decomposed into smaller, more manageable components at the lower levels. This decomposition continues until the project scope is fully defined and all work required to complete the project is represented.</li>

<li class="has-medium-font-size">100% Allocation: At each level of the WBS, the work represented by the child elements should collectively add up to 100% of the work represented by the parent element. This ensures that all project work is captured and accounted for within the WBS.</li>
</ol>

For example, consider a construction project to build a house. The top-level element of the WBS might be "House Construction." This is decomposed into lower-level elements such as "Foundation," "Frame Construction," "Roofing," "Interior Finishing," and "Exterior Finishing." Each of these elements should collectively account for 100% of the work required to complete the "House Construction" phase.

The 100% rule helps ensure that the WBS comprehensively represents the project scope and that no work is overlooked or duplicated. It provides a structured framework for project planning, scheduling, and resource allocation, enabling project managers to effectively manage and control project activities. Additionally, adherence to the 100% rule facilitates accurate cost estimation, progress tracking, and communication of project scope to stakeholders.

<figure class="wp-block-image size-full has-lightbox"><img src="https://pmri.in/wp-content/uploads/2024/04/wbshighlevel.png" alt="" class="wp-image-1176"/></figure>

<figure class="wp-block-image size-full has-lightbox"><img src="https://pmri.in/wp-content/uploads/2024/04/wbs-activity-decomposition-wrenchacademy-1-1.jpg" alt="" class="wp-image-1177"/></figure>

<h5 class="wp-block-heading has-medium-font-size">Work packages</h5>

A work package is a fundamental element of a project's Work Breakdown Structure (WBS). It represents a discrete, manageable unit of work that contributes to the completion of a project deliverable or objective. Work packages are typically decomposed from higher-level project deliverables and further broken down into smaller tasks or activities that can be planned, executed, and tracked.

Here are key characteristics of a work package:

<ol class="wp-block-list">
<li class="has-medium-font-size">Defined Scope: Each work package has a clearly defined scope of work, outlining the specific deliverables, objectives, and outcomes to be achieved.</li>

<li class="has-medium-font-size">Measurable: Work packages are tangible and measurable units of work, with defined criteria for completion and success. They should be specific enough to allow for accurate estimation, planning, and monitoring of progress.</li>

<li class="has-medium-font-size">Assignable: Work packages are assigned to individual team members or groups responsible for executing the work. Assignees are accountable for completing the work package within the specified constraints, such as budget, schedule, and quality standards.</li>

<li class="has-medium-font-size">Time-Bound: Work packages have defined start and end dates, indicating when the work is expected to begin and be completed. Time-bound work packages help project managers track progress, identify delays, and manage project schedules effectively.</li>

<li class="has-medium-font-size">Resource Requirements: Work packages outline the resources, such as personnel, equipment, materials, and budget, needed to accomplish the work. Clear resource requirements enable project managers to allocate resources efficiently and ensure that teams have the necessary support to complete the work.</li>

<li class="has-medium-font-size">Dependencies: Work packages may have dependencies on other work packages, tasks, or project activities. Understanding dependencies helps project managers sequence work effectively, identify critical paths, and manage interdependencies to prevent bottlenecks and delays.</li>

<li class="has-medium-font-size">Control Points: Work packages serve as control points for monitoring and managing project progress. Project managers track the status of work packages, assess performance against predefined metrics or milestones, and take corrective actions as needed to keep the project on track.</li>
</ol>

Work packages provide a structured framework for organizing, planning, and executing project work, enabling project teams to manage complex projects more effectively. By breaking down project deliverables into smaller, manageable components, work packages help streamline project management processes, improve resource allocation, and enhance overall project success.

<h6 class="wp-block-heading has-medium-font-size">Examples of Work Packages for EPC Projects:</h6>

<ol class="wp-block-list">
<li class="has-medium-font-size">Foundation Construction (EPC - Bridge Construction)
<ul class="wp-block-list">
<li>Excavation</li>

<li>Formwork Installation</li>

<li>Reinforcement Placement</li>

<li>Concrete Pouring</li>

<li>Curing and Finishing</li>
</ul>
</li>

<li class="has-medium-font-size">Structural Steel Erection (EPC - Industrial Plant Construction)
<ul class="wp-block-list">
<li>Steel Fabrication</li>

<li>Transportation to Site</li>

<li>Erection Planning</li>

<li>Crane Operations</li>

<li>Welding and Bolting</li>
</ul>
</li>

<li class="has-medium-font-size">Piping Installation (EPC - Oil Refinery Upgrade)
<ul class="wp-block-list">
<li>Pipe Routing</li>

<li>Pipe Cutting and Beveling</li>

<li>Pipe Welding</li>

<li>Pipe Support Installation</li>

<li>Hydrostatic Testing</li>
</ul>
</li>

<li class="has-medium-font-size">Electrical System Installation (EPC - Power Plant Construction)
<ul class="wp-block-list">
<li>Cable Tray Installation</li>

<li>Cable Pulling</li>

<li>Equipment Wiring</li>

<li>Instrumentation Installation</li>

<li>Electrical Panel Assembly</li>
</ul>
</li>

<li class="has-medium-font-size">Commissioning and Testing (EPC - Water Treatment Plant)
<ul class="wp-block-list">
<li>Functional Testing</li>

<li class="has-medium-font-size">Performance Testing</li>

<li>System Integration</li>

<li>Troubleshooting and Debugging</li>

<li>Client Acceptance Testing</li>
</ul>
</li>
</ol>

<h6 class="wp-block-heading has-medium-font-size">Examples of Work Packages for IT Projects:</h6>

<ol class="wp-block-list">
<li class="has-medium-font-size">Requirement Gathering (IT - Software Development)
<ul class="wp-block-list">
<li>Stakeholder Interviews</li>

<li>User Surveys</li>

<li>Requirements Documentation</li>

<li>Use Case Development</li>

<li>Requirement Prioritization</li>
</ul>
</li>

<li class="has-medium-font-size">System Architecture Design (IT - Web Application Development)
<ul class="wp-block-list">
<li>High-Level Architecture Planning</li>

<li>Database Schema Design</li>

<li>Component Specification</li>

<li>Interface Design</li>

<li>Security Architecture</li>
</ul>
</li>

<li class="has-medium-font-size">Frontend Development (IT - Mobile App Development)
<ul class="wp-block-list">
<li>User Interface Design</li>

<li>Screen Prototyping</li>

<li>Frontend Coding (HTML, CSS, JavaScript)</li>

<li>UI/UX Testing</li>

<li>Accessibility Implementation</li>
</ul>
</li>

<li class="has-medium-font-size">Backend Development (IT - E-commerce Platform)
<ul class="wp-block-list">
<li>Database Development (SQL, NoSQL)</li>

<li>Server-Side Programming (Node.js, Python, Java)</li>

<li>API Development</li>

<li>Authentication and Authorization</li>

<li>Integration with External Systems</li>
</ul>
</li>

<li class="has-medium-font-size">Quality Assurance (IT - Software Testing)
<ul class="wp-block-list">
<li>Test Plan Development</li>

<li>Test Case Creation</li>

<li>Functional Testing</li>

<li>Regression Testing</li>

<li>Performance Testing</li>
</ul>
</li>

<li class="has-medium-font-size">Deployment and Release (IT - System Implementation)
<ul class="wp-block-list">
<li>Deployment Planning</li>

<li>Configuration Management</li>

<li>Data Migration</li>

<li>Rollout Strategy</li>

<li>User Training and Support</li>
</ul>
</li>
</ol>

These examples illustrate how work packages break down project deliverables into smaller, manageable tasks or activities, facilitating effective planning, execution, and monitoring of projects in both EPC and IT domains

80-20 rule is a globally applicable rule of thumb or hueristic which can be applied in various scenarios. For example;

<ul class="wp-block-list">
<li class="has-medium-font-size">80% of the wealth is with 20% of the people </li>

<li class="has-medium-font-size">80% of the population is in 20% of the countries </li>

<li class="has-medium-font-size">80% of the inventory cost is from 20% of the items </li>

<li class="has-medium-font-size">80% of the work is done by 20% of the people </li>

<li class="has-medium-font-size">80% of the defects are caused by 20% of the team members </li>
</ul>

The concept of the 80-20 rule can be applied to work packages within a project's Work Breakdown Structure (WBS). In this context, the rule suggests that a minority of work packages (roughly 20%) often account for the majority of project effort or resources (about 80%). This principle emphasizes the importance of identifying and prioritizing the critical few work packages that contribute most significantly to project success.

Here's how the 80:20 rule can be associated with work packages:

<ol class="wp-block-list">
<li class="has-medium-font-size">Identification of Critical Work Packages: Project managers analyze the WBS to identify the critical few work packages that have the greatest impact on project objectives, timelines, and deliverables. These work packages typically involve complex tasks, high resource requirements, or significant dependencies with other project components.</li>

<li class="has-medium-font-size">Resource Allocation: The 80-20 rule suggests that a significant portion of project resources and effort should be allocated to the critical few work packages that contribute most to project success. Project managers prioritize resource allocation, staffing, and budgeting to ensure that these work packages receive adequate attention and support.</li>

<li class="has-medium-font-size">Risk Management: Work packages identified as critical according to the 80-20 rule are often associated with higher levels of risk due to their complexity, dependencies, or impact on project outcomes. Project managers focus risk management efforts on mitigating risks associated with these critical work packages to minimize potential disruptions or delays.</li>

<li class="has-medium-font-size">Time Management: The critical few work packages identified through the 80-20 rule may also consume a significant portion of project time and effort. Project managers prioritize scheduling, task sequencing, and resource allocation to ensure timely completion of these critical work packages, thereby minimizing project delays and optimizing overall project schedules.</li>

<li class="has-medium-font-size">Monitoring and Control: Project managers closely monitor progress and performance of the critical work packages throughout the project lifecycle. By focusing monitoring and control efforts on these key areas, project managers can quickly identify deviations, address issues, and take corrective actions to keep the project on track and mitigate potential risks.</li>
</ol>

Overall, the application of the 80-20 rule to work packages within a project's WBS helps project managers prioritize resources, manage risks, optimize schedules, and enhance overall project performance by focusing efforts on the critical few work packages that drive project success.

The concept of the 8-80 rule can also be applied to work package sizing within a project's Work Breakdown Structure (WBS). In this context, the rule suggests that work packages should ideally be sized to be neither too small (less than 8 hours) nor too large (more than 80 hours).

Here's how the 8-80 rule can be associated with work package sizing:

<ol class="wp-block-list">
<li class="has-medium-font-size">Avoiding Micro-Tasks (Less Than 8 Hours): Work packages that are too small, typically less than 8 hours in duration, may not provide sufficient granularity for effective tracking and management. Micro-tasks can lead to excessive administrative overhead, increased complexity in scheduling, and difficulty in accurately estimating progress. Additionally, breaking down work into overly small tasks can hinder team productivity and motivation. Therefore, project managers aim to avoid excessively small work packages by consolidating tasks and grouping related activities.</li>

<li class="has-medium-font-size">Preventing Macro-Tasks (More Than 80 Hours): Conversely, work packages that are too large, exceeding 80 hours in duration, may become unwieldy and difficult to manage. Macro-tasks can pose challenges in resource allocation, scheduling, and progress tracking. They may also increase the risk of delays and dependencies, as well as hinder the identification of potential issues and risks. To prevent overly large work packages, project managers decompose project deliverables into smaller, more manageable components, ensuring that work packages are sized appropriately for efficient execution and control.</li>
</ol>

By adhering to the 8-80 rule in work package sizing, project managers aim to achieve a balance between granularity and manageability. Work packages sized within the optimal range of 8 to 80 hours enable effective tracking, resource allocation, and progress monitoring, thereby enhancing project control and delivery efficiency. Additionally, appropriately sized work packages facilitate clearer communication, better task assignment, and improved team collaboration, contributing to overall project success.

100% rule suggests that 100% of the scope must be covered in the Work Breakdown Structure (WBS). Once the WBS is finalised, all further planning will be based on the WBS, hence WBS must cover the entire scope of work of the project.

<h5 class="wp-block-heading has-medium-font-size">WBS dictionary</h5>

WBS dictionary provides additional information about the work packages so that the person who is really performing the work have sufficient information to do it right the first time without running around for clarifications.

<figure class="wp-block-image size-full"><img src="https://pmri.in/wp-content/uploads/2024/04/wbs-dictionary.png" alt="" class="wp-image-1178"/></figure>

</blockquote>

Cancel