1/14
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Work Breakdown Structure (WBS)
A project management tool that organizes tasks into smaller, manageable units for better understanding, estimation, and tracking.
WBS Models
Three common formats to present a WBS:Outline, Organizational Chart, and Concept Map.
Outline Model
A simple, hierarchical list of tasks, suitable for smaller projects, presenting tasks in an easy-to-read format.
Organizational Chart Model
A hierarchical chart that breaks tasks into levels, ideal for larger projects, showing task dependencies.
Concept Map Model
A visual representation of task relationships, useful for agile projects where tasks can be completed concurrently.
Purpose of WBS
Helps understand project scope, estimate time and budget, illustrate task relationships, and allocate resources.
Work Packages
Core tasks or pieces of work within the WBS that are essential for project completion.
Level Indicators
A numbering system (e.g., 1, 1.1, 1.1.1) used to show the hierarchy of tasks in a WBS.
Links
Represent relationships between tasks, particularly task dependencies, in a hierarchical format or concept maps.
Guidelines for Creating a WBS
Recommendations to avoid excessive detail, ensuring clarity and focus on project goals.
Deliverable Basis
The lowest level of detail in a WBS should be acceptable for delivery to the customer.
Risk Management
Addressing specific risks during the decomposition of tasks in the WBS.
Organizational Guidelines
Adhering to internal standards, including quality control and testing protocols, when creating a WBS.
Critical Path
The sequence of essential tasks within the WBS that must be completed for the project to finish on time.
Task Dependencies
Relationships between tasks that determine the order in which they must be completed.