Project Management Professional (PMP) for engineering project management roles
1 Introduction to Project Management
1-1 Definition of Project Management
1-2 Project Management Framework
1-3 Project Management Knowledge Areas
1-4 Project Management Processes
1-5 Project Life Cycle
2 Project Integration Management
2-1 Develop Project Charter
2-2 Develop Project Management Plan
2-3 Direct and Manage Project Work
2-4 Monitor and Control Project Work
2-5 Perform Integrated Change Control
2-6 Close Project or Phase
3 Project Scope Management
3-1 Plan Scope Management
3-2 Collect Requirements
3-3 Define Scope
3-4 Create WBS
3-5 Validate Scope
3-6 Control Scope
4 Project Time Management
4-1 Plan Schedule Management
4-2 Define Activities
4-3 Sequence Activities
4-4 Estimate Activity Durations
4-5 Develop Schedule
4-6 Control Schedule
5 Project Cost Management
5-1 Plan Cost Management
5-2 Estimate Costs
5-3 Determine Budget
5-4 Control Costs
6 Project Quality Management
6-1 Plan Quality Management
6-2 Perform Quality Assurance
6-3 Control Quality
7 Project Human Resource Management
7-1 Develop Human Resource Plan
7-2 Acquire Project Team
7-3 Develop Project Team
7-4 Manage Project Team
8 Project Communications Management
8-1 Plan Communications Management
8-2 Manage Communications
8-3 Control Communications
9 Project Risk Management
9-1 Plan Risk Management
9-2 Identify Risks
9-3 Perform Qualitative Risk Analysis
9-4 Perform Quantitative Risk Analysis
9-5 Plan Risk Responses
9-6 Control Risks
10 Project Procurement Management
10-1 Plan Procurement Management
10-2 Conduct Procurements
10-3 Control Procurements
10-4 Close Procurements
11 Project Stakeholder Management
11-1 Identify Stakeholders
11-2 Plan Stakeholder Management
11-3 Manage Stakeholder Engagement
11-4 Control Stakeholder Engagement
12 Engineering Project Management Specialization
12-1 Engineering Project Life Cycle
12-2 Engineering Project Planning and Scheduling
12-3 Engineering Project Cost Estimation
12-4 Engineering Project Risk Management
12-5 Engineering Project Quality Management
12-6 Engineering Project Procurement Management
12-7 Engineering Project Stakeholder Management
12-8 Engineering Project Communication Management
12-9 Engineering Project Integration Management
12-10 Engineering Project Human Resource Management
13 Tools and Techniques for Engineering Project Management
13-1 Project Management Software
13-2 Scheduling Tools
13-3 Cost Estimation Tools
13-4 Risk Management Tools
13-5 Quality Management Tools
13-6 Communication Tools
13-7 Stakeholder Management Tools
13-8 Procurement Management Tools
14 Case Studies and Practical Applications
14-1 Case Study Analysis
14-2 Practical Application of Project Management in Engineering Projects
14-3 Lessons Learned from Engineering Projects
15 Certification Preparation
15-1 Overview of PMP Certification Exam
15-2 Exam Format and Structure
15-3 Study Tips and Strategies
15-4 Practice Questions and Mock Exams
15-5 Certification Application Process
3.4 Create WBS

3.4 Create WBS - 3.4 Create WBS - 3.4 Create WBS

Creating a Work Breakdown Structure (WBS) is a fundamental process in project management that involves breaking down the project scope into smaller, more manageable components. The WBS provides a clear and structured approach to planning, executing, and controlling the project's work. It ensures that all project deliverables and tasks are identified and organized, making it easier to manage the project effectively.

Key Concepts

1. Deliverable-Oriented Hierarchical Decomposition

The WBS is a deliverable-oriented hierarchical decomposition of the project. This means that the project is broken down into major deliverables, which are then further divided into smaller sub-deliverables and tasks. The hierarchy helps in organizing the project work in a logical and systematic manner.

Example: For a construction project, the major deliverables might include "Foundation," "Structural Frame," and "Roofing." Each of these deliverables would then be broken down into smaller tasks such as "Excavation," "Pouring Concrete," and "Installing Steel Beams."

2. Control Accounts

Control Accounts are management control points where scope, budget, schedule, and resources are integrated and managed. They are placed at various levels of the WBS to provide a framework for tracking and controlling project performance.

Example: In a software development project, a Control Account might be set up for the "User Interface Design" deliverable. This account would include all tasks related to designing the user interface, such as "Wireframing," "Prototyping," and "User Testing."

3. Work Packages

Work Packages are the lowest level of the WBS where the project work is planned, executed, and controlled. Each Work Package represents a specific task or set of tasks that can be assigned to a team member or a group of team members. Work Packages are the basis for detailed planning and cost estimation.

Example: In an engineering project to design a new product, a Work Package might be "Design Component A." This package would include all tasks necessary to complete the design of Component A, such as "Conduct Design Review," "Create CAD Model," and "Perform Stress Analysis."

4. WBS Dictionary

The WBS Dictionary is a document that provides detailed information about each element of the WBS. It includes descriptions of the work packages, assigned resources, schedule milestones, and other relevant details. The WBS Dictionary ensures that all stakeholders have a clear understanding of the project's scope and deliverables.

Example: For a marketing campaign, the WBS Dictionary would include detailed descriptions of each Work Package, such as "Design Advertisements," "Create Social Media Content," and "Conduct Market Research." Each entry would specify the tasks involved, the responsible team members, and the expected completion dates.

5. Zero-Level, First-Level, and Subsequent Levels

The WBS is structured in levels, starting with the Zero-Level, which represents the entire project. The First-Level includes the major deliverables, and subsequent levels break down these deliverables into smaller components. This hierarchical structure helps in organizing and managing the project work effectively.

Example: In a project to develop a new software application, the Zero-Level would be the entire project, the First-Level might include "Front-End Development," "Back-End Development," and "Testing." Subsequent levels would further break down these deliverables into specific tasks and Work Packages.