1. Capacity Planning Dashboard
  2. Features
  3. Work packages
Feature · Work packages

Work packages

Organize project work into owned delivery blocks with dates, hour budgets and visible task demand.

OverviewBlocked Tasks
Capacity Planning Dashboard · Work packages

Blocked Tasks

Tasks

New
Task keyTitleProjectWork packageAssigneePriority
TK-967Blocked tsk-858PRJ-2889WP-6436Low
TK-239Blocked tsk-853PRJ-4101WP-5018Medium
TK-857Blocked tsk-832PRJ-2002WP-4924High
TK-203Blocked tsk-513PRJ-7985WP-1623Critical
TK-244Blocked tsk-213PRJ-1460WP-7615Low
6 of 6 records
TK-967Tasks · TSK-72050
Low
TitleBlocked tsk-858
ProjectPRJ-2889
Work packageWP-6436
Due date16 Oct
StatusBlocked
Example screen with sample data

What you can do

Make the planned block of work recognizable

A work package groups tasks inside a project. The Project Manager records its subject, owner, start and end dates and hour budget so the team can discuss a manageable delivery block. Keep the project link visible when the same people contribute to packages across several engagements.

The package’s task estimates and actual hours provide evidence for the planning conversation. Compare those values with the budget hours while reviewing the tasks that produced them. A change in the package’s dates can affect several people’s commitments, so discuss it with the relevant managers before updating the plan.

How the work is organized

  • Package scope. Give the subject and description enough detail for the team to recognize the intended outcome. Assign an owner who can explain what belongs inside the package and what still needs a separate planning decision.
  • Delivery window. Use the start and end dates to show when the package is intended to run. Check the parent project’s dates and the tasks assigned inside it before agreeing a change to the window.
  • Effort comparison. Keep budget hours alongside task estimates and actual hours. When the figures diverge, open the underlying tasks and discuss the work involved before treating the difference as a staffing decision.

What to agree during setup

Agree how broad a work package should be. A package that is too vague makes it difficult to assign meaningful tasks, while a consistent subject and description help the owner explain the work at review. Decide who may revise the hour budget and what decision record is needed when the scope changes.

Define when the package becomes in progress, Blocked or Done. The Project Manager should review task outcomes before updating the package state. Agree what to do when a task’s optional project link disagrees with its package’s project, and check those links during import so effort is discussed under the intended engagement.

Check the handoff on an actual case

A reporting project has a data-preparation package budgeted at 60 hours. Its tasks are estimated at 48 hours when planning begins. The owner later identifies an additional extraction task estimated at 20 hours and asks the Project Manager to revisit the package.

The manager examines the task detail and discusses the resulting 68-hour estimate with the Delivery Lead. The team can revise scope, dates or assignments under its review procedure. Keep the package and its tasks aligned after the decision so the capacity discussion uses the same commitment. During the rehearsal, block a task that affects the package and ask the owner to explain whether the package should also become Blocked. Record the outcome before the next planning cycle begins.

What your team sees

  • Package schedule — Open work packages with their owner, planned start and end, budget hours and task effort.
  • Tasks In Flight — Active task work that helps the package owner explain delivery progress.

Follow the work through

Prepare packages during capacity planning and assignment, then follow execution through task delivery and recorded time.

What it keeps track of

Data model
Work packages
Groupings of work inside a project.
Projects
Engagements delivered for an organization, with budget and schedule.
Tasks
Individual pieces of work assigned to a delivery team member.
Team members
Delivery staff with role, practice and weekly capacity.
Review decisions
Recorded approval decisions on delivery subjects.

Who uses it

Permissions
Project Manager
, Delivery Lead, Developer, QA Engineer.
The manager maintains the package, the lead reviews commitments, and assigned staff provide the task evidence used to revisit the plan.

Set up Capacity Planning Dashboard your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started