At the front posts, the focus was on setting goals, forming a team for the project, managing conflicts, and the division of responsibility in the middle of the team. Today, please go to the project planning tools and look at one of these tools – WBS (Work Breakdown Structure) or the hierarchical structure that works with the project.
To be fair, the WBS is based on the results of the completed hierarchical decomposition of the work, as the project team can work to achieve the goals of the project and create the results of the project.
This tool is approved by the project manager simultaneously with the project management team at the planning stage.
The main goal is to structure and structure the entire project. In other words, WBS is responsible for eliminating all work planned in the project. First, let’s move on to the rules of the WBS, I want to focus on two aspects 1) the WBS does not include: a project implementation schedule;
A document that replaces the project implementation plan;
Perelikom dіy chi vіkh.
This aspect should not be forgotten and will be replaced by the concept that the directness of the WBS will determine the structure of the project and also on the basis of this structure there will be a PLAN for the project and an implementation schedule.
The next aspect about how to predict this is: 2) Important steps to store WBS are shown below: WBS Now you can go to the algorithm for storing WBS.
Algorithm number 1: Start with the goals of the project (the corresponding areas of the project);
Rearrange the output results, the necessary achievement of goals – move them horizontally;
For the skin outcome, identify the key blocks or actions necessary for your own safety (inform the descriptions as best as possible);
Detail in ties to the required level of detail;
Ensure that the project team knows the key aspects of the project and develop the WBS from them at once.
Algorithm number 2 (Vikorist stickers and flipchart): Give participants the following message: “What needs to be done to implement the project?”;
Team members record their responses on stickers; (the time it takes to commit to the project);
Those close to the place of the Zavdannya are grouped behind the stacks/stacks;
Zavdannya, so as not to be wasted in the same pile, stick to it hard;
After which you can guess the name of the Category (to the column/stop), write it down on the flipchart and put sticky notes under each category.
In this way, we select the WBS, the example of which is shown below (the example itself is shown in order to show the essence of the tool. This WBS is not exclusively for the implementation of the CRM project):
