Use WBS deliverables and scope to plan ownership and timing
A diagram or table that organizes what a project must produce and the work required into a hierarchy is called a work breakdown structure, or WBS. It provides a basis for assigning work and developing a schedule. (PMI WBS practice standard overview)
For a website launch, identify what must be completed and how completion will be judged: published pages, approved content, usable contact functions, and launch checks. Check that copy preparation, photographs, and submission tests are covered, then plan the activities, ownership, and timing needed to deliver that scope.
Organize the scope around deliverables
A WBS connects the overall project to major deliverables and their components. PMI describes it as a structure for deliverables and scope, distinct from the sequence and timing of execution. (PMI WBS practice standard overview)
For a website, defining the scope can expose missing preparation: photographs without publication permission, or a contact form without a delivery check. These are practical examples of applying the structure.
| Planning document | What it clarifies | Example |
|---|
| WBS | Deliverables and work scope | Service pages, contact functionality, launch review |
| WBS element description | Included work and completion criteria | Content boundaries, reviewers, acceptance criteria |
| Schedule | Activity sequence, dependencies, and timing | Add approved copy to the page |
| To-do list | Activities to execute | Draft the service description |
Define scope and completion criteria
Describe the included work and completion criteria for each deliverable so its owner and reviewer understand the same scope. For a website launch, connect the page and function requirements to the copy and images needed.
Define what a website launch includes
Make the completion criteria observable: three published pages with inquiry delivery tested, for example. State the work included and the work outside this project's scope.
This example uses identifiers to show the relationship between deliverables and their components.
| Identifier | Deliverable or managed scope | Example completion criterion |
|---|
| 1 | Published website | Required pages and functions are available |
| 1.1 | Page content | Copy and media have been reviewed |
| 1.1.1 | Service copy | Scope and prices reflect the actual offer |
| 1.1.2 | Business information | Business name, responsible person, and contact details are correct |
| 1.1.3 | Publication images | Images and publication permission are available |
| 1.2 | Published pages and functions | Content is in place and required interactions work |
| 1.2.1 | Contact functionality | A test inquiry arrives and acknowledgment appears |
| 1.3 | Launch review | Display and links have been checked and approved |
Expand the example to cover the actual project. For content planning, see A one-page website structure.
Describe the work and acceptance criteria for each element
Record the deliverable, included work, responsible person, reviewer, and acceptance criteria. A WBS dictionary describes elements in detail, as explained in NASA's handbook. (NASA WBS handbook)
Copy alone leaves questions about whether the work includes a draft, editing, price verification, and approval. Define those boundaries for the service-copy element.
Use work packages that people can understand, estimate, and assess for completion. Dividing them solely to meet a short time limit can create more administration; choose a level that suits how the work will be managed.
Plan ownership and timing from the defined scope
Use the deliverables in the WBS to plan activities, owners, and dates. When a request changes, update both the scope and the execution plan.
Turn the scope into activities, ownership, and dates
Identify activities needed to produce each deliverable. Service copy might require gathering information, drafting, review, and revision.
Reflect dependencies between activities in the schedule. Approved copy may be needed before the page content can be finalized. Include ownership, estimates, and reviewers so the team knows what happens when.
Check for duplicated work and missing support or review. NASA describes the WBS as a framework connecting scope with project-management information. (NASA WBS handbook)
Update both scope and schedule when requests change
A request for another page or function adds a deliverable and associated work. Record that scope and allow for content, implementation, and review time in the schedule.
Extending dates alone leaves the added work undocumented. Expanding scope alone leaves ownership and launch dates unchanged. Agree who approves a change and how its effect on cost and timing will be assessed.
Share the completion criteria before planning execution
Define deliverables and scope in the WBS, and record acceptance criteria in the element descriptions. Agree with each owner and reviewer on what counts as complete. Use that scope to create activities, a schedule, and daily to-dos. Keep additional requests connected to the same plan.
When reviewing a large project, look for a clear deliverable, a responsible person, and a reviewer for each managed unit of work.
For a website launch, include copy and image preparation, page setup, and the launch review in the WBS, then choose a tool for building the site.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To build a website using the copy and images planned in your WBS, give SpreadSite a try!
Build a website with SpreadSite →
