01

What changes when a project has a structure

A project planned with the Work Breakdown Structure organizes phases, sub-phases and tasks with responsibility, status, priority, dates, milestones, hour budgets and progress in a single plan.

The structure, Gantt timeline and combined views keep hierarchy and planning together, so managers and teams see priorities, progress and deadlines in the same context.

02

How the plan is built, step by step

Steps

  1. Open the project register and identify the project to oversee through search, filters and sorting.
  2. Set up the WBS by defining phases and sub-phases with responsibilities, priorities and associated dates.
  3. Assign milestones, hour budgets and progress status to each task in the structure.
  4. Move from the structure view to the Gantt timeline to verify the sequence of phases.
  5. Link tasks to the board to project them into the company workflow columns.

03

What is needed before starting

Prerequisites

  • A project already present in the portfolio register, with client and context identified.
  • People and assignments defined, consistent with authorized access to the Nebulas platform.
  • Project types, statuses and tags already set up on the platform.

04

A hypothetical case: an implementation project

Hypothetical example: an agency starts an implementation project. The manager creates in the WBS the phases of analysis, development and testing, each with an hour budget and delivery milestones.

With the Gantt view the team verifies the sequence of the analysis, development and testing phases, while the board shows tasks in progress and those blocked.

05

What to check before starting the project

  • Each WBS phase has an assigned responsible person, status and priority.
  • Dates and milestones are consistent in the Gantt view.
  • The hour budget has been set for the tasks in the structure.
  • The board reflects the same company workflow used for other projects.

06

How Nebulas Projects supports this planning

Nebulas Projects brings together portfolio, WBS plan, timeline, tasks and logged hours in one cloud workspace, keeping the context of client, people, assignments, types, statuses and tags from the platform.

Timesheets organize entries by date, project and WBS task, with daily, weekly and monthly views showing detail and totals to check actuals against the planned hour budget.

07

Recommended sequence for a new project

Steps

  1. Register the project in the portfolio with client and initial status.
  2. Build the WBS with phases, responsibilities, priorities and hour budgets.
  3. Check the sequence with the Gantt view before assigning tasks to the team.
  4. Activate the board to follow daily progress of WBS tasks.
  5. Periodically check timesheets to compare logged hours with budget.

08

Next step

Anyone leading a project team can start with a single project: build the WBS with phases and hour budgets, activate the board and check after a week whether timesheet actuals match what was planned.

FAQ

Frequently asked questions

What distinguishes the WBS from a simple task list?

The WBS organizes phases and sub-phases with responsibility, status, priority, dates, milestones, hour budgets and progress, not just a list of individual tasks.

How can you check whether the planned hour budget is being met?

Timesheets record date, project and WBS task with daily, weekly and monthly views, allowing actuals to be compared against what was planned.

Does the board replace the WBS or complement it?

The board projects WBS tasks into the company workflow columns, so it complements the structure by showing priority, dates, status and operational path.

✓

Sources and verification