Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. All product and project work, including project management work, is represented by the WBS.

The two outputs of the Create WBS process are the scope baseline and project document updates. The key inputs into the Create WBS process are the scope management plan, templates and lessons learned from past projects (organizational process assets) and industry-specific WBS standards (enterprise environmental factors).

The Create WBS process is performed once or at predefined points in the project.

Create WBS Tasks

A separate Project Management folder can be used to manage project management activities (as opposed to project work). In the Project Management folder, create the Create WBS task with two subtasks corresponding to the outputs of the Create WBS process: Develop scope baseline and Update project documents.

Provide instructions in the task and subtask description on how to create WBS, develop scope baseline, and update project documents.

Decomposition of the total project work into work packages usually includes the following steps:

  • Identifying deliverables
  • Analyzing deliverables
  • Structuring WBS
  • Organizing WBS
  • Decomposing WBS
  • Assigning ID codes to WBS components

A WBS structure may be created using a top-down approach, bottom-up approach or using a combination of the two.

As you build your WBS, you often find gaps in scope. As you do it, you must go back and update the scope statement and the scope management plan.

Project documents that may be updated as a result of this process include assumption log and requirements documentation.

Subsequently, you must update the baseline (along with the scope management plan, project scope statement, WBS, and WBS dictionary) to incorporate the new work packages for work that is added to the scope through change control so that you can continuously monitor your progress against the plan. As a result, it is crucial to keep all of the scope planning documents in sync with one another.

Add document relationships to the corresponding task.

Create Scope Baseline Doc

In the Docs section, create the Scope Baseline document. Provide document structure and content manually, paste the content from an MS Word or MS Excel document (ClickUp will do its best to transform the content into the ClickUp format) or create the doc from a company template.

The scope baseline is the approved version of a scope statement, WBS, and the associated WBS dictionary. Components of the scope baseline include:

  • Project scope statement
  • WBS
  • Work package
  • Planning package
  • WBS dictionary

Share Scope Baseline Doc

The scope baseline can be shared with:

  • Project sponsor(s): the person who formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
  • Project management team: the members of the project team who are directly involved in project management activities
  • Project team: a set of individuals performing the work of the project to achieve its objectives

Here are your sharing options:

  • Everyone in the workspace (does not include guests)
  • Specific people and teams, including guests
  • People you invite to your workspace while sharing a doc
  • Specific tasks or locations

You can also:

  • Export a doc
  • Share publicly
  • Copy the Internal link to share it with your team

You can also use similar sharing options with individual pages:

  • With workspace members using the internal link
  • Export the page
  • Share publicly

Pages always inherit permissions from the doc they live in.

When sharing with specific people, you can set their permissions.

Leave a Reply

Your email address will not be published.