These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- OKR Tracking System
- Features
- Work packages and tasks
Work packages and tasks
Connect assigned tasks to work packages and follow their status on a board.
OverviewBlocked Tasks×
OKR Tracking System · Work packages and tasks
New
Blocked Tasks
Tasks
| Task key | Title | Work package | Assignee | Due date | Status | |
|---|---|---|---|---|---|---|
| TK-622 | Blocked tsk-583 | WP-3669 | 06 Oct | Blocked | ||
| TK-212 | Blocked tsk-499 | WP-6195 | 04 Oct | Blocked | ||
| TK-743 | Blocked tsk-672 | WP-4254 | 05 Oct | Blocked | ||
| TK-565 | Blocked tsk-649 | WP-2028 | 09 Oct | Blocked | ||
| TK-427 | Blocked tsk-583 | WP-6512 | 23 Oct | Blocked |
6 of 6 records
TK-622Tasks · TSK-94774
BlockedTitleBlocked tsk-583
Work packageWP-3669
Due date06 Oct
PriorityLow
What you can do
Plan the work behind a result
A work package groups tasks under an objective. It carries an owner, start and end dates, estimated hours and status. Each task has a title, assignee, priority, due date, estimate, actual hours and percent complete. The task can also link directly to the objective. Work package totals and hours variance give the manager a place to compare the plan with recorded work.
The work package gives a manager a stable boundary for reviewing several tasks together. When an assignee changes task status, the board reflects the new state. The manager can then compare due dates and assigned hours without copying the task into a separate tracker or losing the objective link.
How the work is organized
- Plan the package. The Project Manager gives the work an objective, owner, dates and estimate.
- Assign the task. The assignee sees its priority, due date and place in the package.
- Review on the board. The manager compares blocked and in-review tasks with their source records.
What to agree during setup
Agree how tasks move through backlog, in progress, in review, blocked and done. Define who sets estimates, who may revise due dates and how work packages are closed. Review the relation between task, work package and objective for imported work. Rehearse one task in progress and one blocked task under the same package. Have the manager check the package estimate, each assignee and the blocker owner before revising dates.
Check the handoff on an actual case
A project manager creates a work package for an active objective and assigns a high-priority task. The assignee moves the task from backlog to in progress, then to in review. If a dependency stops work, the assignee marks it blocked. The manager sees that task on the board and in Blocked Tasks, then follows the related blocker record before moving the task again. The assignee records the next task status on the source task. If the due date changes, the Project Manager checks the package end date and asks whether the key result target date still gives the team enough time. The manager checks that the package and objective still reflect the delivery schedule.
What your team sees
- Task Board by Status — Assigned work grouped by its current task status.
- Blocked Tasks — Tasks that need an owner and a next action.
Follow the work through
What it keeps track of
Data model- Work packages
- Groupings of work inside a project.
- Tasks
- Individual pieces of work assigned to a delivery team member.
- Objectives
- Engagements delivered for an organization, with budget and schedule.
- Team members
- Delivery staff with role, practice and weekly capacity.
Who uses it
Permissions- Project Manager
- , Team Member.
- The Project Manager plans and reviews the package; the Team Member updates assigned task status and hours.
Set up OKR Tracking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.