How to draw a work breakdown structure diagram

This is a very valuable question. In the process of solving your problem, I also learned a lot of important professional knowledge about project management that I didn't notice. Thank you very much. . . Let's get down to business:

I. Definition of project breakdown structure:

First, the project breakdown structure (WBS) is a management tool or "method". WBS is one of the important tools and technologies used in scope planning. It is a delivery-oriented grouping of project elements. It organizes and defines the whole project scope, and the work not included in WBS will be excluded from the project scope. It is a hierarchical tree of the final details to be completed or produced by the project team during the project process, and the completion or output of all these details constitutes the scope of work of the whole project "; "The project breakdown structure is the baseline of a project implementation process, which defines the final' deliverable' of the project, is a reference for evaluating the success of the project, and can also be used as an important judgment basis for evaluating project members."

Simply put, the "project breakdown structure" is to decompose a project according to certain principles-the project is decomposed into tasks, and the tasks are decomposed into tasks, and then each task is assigned to everyone's daily activities until it can't be decomposed. .

"Work Breakdown Structure Diagram" is a list of all activities necessary to implement the project and create the final product or service, and it is the basis of production status management, schedule management, capital control, quality management and resource allocation.

Second, the creation process of WBS:

The process of establishing WBS is:

1. Get ScopeStatemet or StatemetofWok (when contracting subprojects).

2, convene relevant personnel, collective discussion of all major project work, determine the project work breakdown.

3. Break down the project work. If there is a ready-made template, you should try to use it.

4. Draw the hierarchy diagram of WBS. Some work at a higher level of WBS can be defined as subprojects or sub-life cycle stages.

5. Divide the deliverables of major projects into smaller, manageable components or work packages. The work package must be detailed enough to estimate the work package (cost and duration), arrange the progress, make the budget, and assign the responsible personnel or organizational units.

6. Verify the correctness of the above decomposition. If it is found that lower-level projects are unnecessary, modify the composition.

7. If necessary, establish a numbering system.

8. With the progress of other planned activities, WBS will be continuously updated or revised until all work is covered.

9. Check whether WBS is defined completely and all tasks of the project are decomposed completely. Please refer to the following standards:

The status and completion of each task can be quantified.

The beginning and end of each task are clearly defined.

Every task has a deliverable.

The construction period is easy to estimate and within the acceptable period.

It is easy to estimate the cost.

Each task is independent.

Third, the basic principles:

1, the main objectives are gradually refined and decomposed, and the minimum daily activities can be directly assigned to individuals;

2. In principle, each task should be decomposed until it can no longer be decomposed;

3. Daily activities should correspond to people, time and capital investment.

Fourth, the specific requirements:

1. The task should be in one place in WBS, and it should only appear in one place in WBS.

2. The content of the task in WBS is the sum of all WBS projects under it.

3. A WBS project can only be handled by one person. Even though there may be many people doing it, only one person is responsible, and others can only be participants.

4.WBS must be consistent with the implementation methods in actual work.

5. Project team members should actively participate in the creation of WBS to ensure the consistency of WBS.

6. Each WBS project must be recorded to ensure an accurate understanding of the scope of work included and excluded.

7.WBS should not only maintain the work content of the project normally according to the scope specification, but also adapt to the inevitable changes.