Task delivery

Tasks sit under a work package. A task can name an assignee, project, priority, planned hours and due date. The team records actual hours, percent complete and completion time as delivery proceeds. Task status distinguishes Backlog, in progress, in review, Blocked and Done. The saved Task Board by Status presents those records as a kanban screen for the delivery team.

A package is still the change’s governing record. Moving a task to Done does not accept the package. The Project Manager compares task effort with the package’s budget hours and the impact assessment before sending a revision to the Independent Reviewer. A blocked task may affect that decision even if the package’s headline date has not changed.

• Plan the lines. The Project Manager creates tasks under the package, with line numbers and planned hours.
• Assign and progress. Delivery Contributors work from the board and update the status and actual effort of their assigned tasks.
• Reconcile the package. The Project Manager reviews task totals and unresolved work before advancing the package.

Agree task naming, ownership and the meaning of in review for your team. Decide whether tasks are broken down by deliverable, discipline or handoff. The dependency field is text, so establish a clear convention for references if the team uses it. Agree when contributors record actual hours and how the Project Manager treats work that exceeds the estimate. Make the due date visible on the task and package so the two schedules can be compared.

A task can carry a revision. When the package scope changes, decide which task lines must be updated and how the new estimates relate to the current assessment. Do not hide added work inside an old line with no explanation. The board helps people see current status, while the package and assessment explain why the work exists.

The Project Manager plans a change to a project’s approval screen: one task covers the new form, one covers reviewer behavior and one covers verification. Each has planned hours and an assignee. A Delivery Contributor moves the form task from Backlog to in progress and records actual time. The verification task becomes Blocked when the expected reviewer behavior is unclear.

Before sending the package to Review, the Project Manager reads the Task Board by Status and finds the blocked line. They clarify the requirement with the Business Analyst, update the task and its planned hours, and compare the new total with the impact assessment. The reviewer then sees a package whose scope and work plan agree. Marking the other tasks Done would not have resolved the missing requirement.

• Task Board by Status — Tasks grouped by Backlog, in progress, in review, Blocked and Done.
• Tasks due — Due work with its assignee, parent package and planned hours.

Task execution follows the plan and effort check. Scope to review shows when the package is ready for a decision.