“WBS” word is used in QuickPlan and our WBS apps, but they are NOT the same thing.
The WBS app helps break down the WORK into a tree structure. QuickPlan is a project planning app that helps organize the TASKS into a tree structure and displays it in the Gantt chart.
From the process perspective, we can use the output of the WBS app as the input of the QuickPlan app, and we cannot treat the QuickPlan project plan as the input of the WBS app.
Different process steps
- The WBS app is used to break down the work from a very high level to an appropriate level to define the project scope and perform the estimating. Usually, it is in the step before the SOW (contract).
- QuickPlan app helps plan the project tasks to be executed by the team and track the execution after the project starts with a clear scope. More details on why we choose QuickPlan for project management.
A “WORK” is NOT a “TASK”
- In the work breakdown structure (WBS), we usually divide the work into DELIVERIES. Of course, we can also divide the work into HIGH - LEVEL tasks. When we create the work breakdown structure to prepare for the start of the project, we have no information to confirm the detailed tasks.
- In a project plan, we divide the work into executable tasks and assign them to project members. More details about why we are choosing QuickPlan for the project management.
There is a NO one-to-one relationship between a WORK and a project plan TASK.
- A WORK (a deliverable or parent task) can have a relationship to multiple tasks in the project plan.
- Some WORKS may have a relationship to a task in the project plan.
For example, there is a WORK in the WBS document: “User Login.” After the project is started, we may need some tasks for the WORK, but the related tasks are not unique to the WORK. Like:
- Tasks for the security
- Login page
- Tasks for testing
- …
The real need might be a PROJECT SCHEDULE REPORT with the TREE VIEW, which is similar to the user interface of the WBS app.
Although the two apps use the same conceptual name and are loosely related, the two concepts are different.
For reporting purposes, it may be necessary to display the project status in a work breakdown structure VIEW, so QuickPlan supports exporting a project to a WBS file.
- For reporting purposes only.
- Not for processing purposes. From a process perspective, we can use the output of the WBS app as input to the QuickPlan app, and we cannot treat the QuickPlan project plan as input to the WBS app.