Task workload

A task identifies the piece of work a person will perform within a work package. The Project Manager records the title, priority, assignee, estimate and dates, with a description that explains the expected result. The package link gives the assignment its delivery context when the person is working across projects.

Use the task board to follow work from Backlog into progress and review, then Done. Blocked work needs a conversation about what prevents the next step and which person should resolve it. Keep the task current so the capacity review can distinguish new demand from work that is already underway or waiting on someone else.

• Assignment ownership. Choose the team member who will perform the task and check the dates against their other commitments. Agree changes with the person before moving an assignment between projects or shifting its due date.
• Progress evidence. Record actual hours and completion information consistently with the team’s operating procedure. Use the task description and linked evidence to explain progress when the state alone is too broad for a delivery decision.
• Blocked work. Keep a blocked task recognizable in the shared queue and discuss its priority with the Project Manager. Record a related issue or risk when the concern needs its own owner and follow-through.

Agree what makes a task ready to start and what the team checks before moving it into review. Decide who records the final Done state after reviewing the result. Use the same conventions across projects so a board discussion does not mix different meanings of completion.

Define the relationship between task actual hours and time booked by team members. Review the source records before relying on an effort comparison, and settle how corrections will be handled. Test the personal assignment screen with each pilot user so the person sees the correct team-member identity and work.

A developer receives a data-extraction task estimated at 12 hours, due before the package’s review window. They start the work and later discover that an input file is unavailable. The developer marks the task Blocked and raises an issue with severity and project context so the manager can coordinate the response.

The Project Manager uses the blocked task to discuss whether another assignment can proceed in the meantime. When the input becomes available, the developer resumes work and sends the result for review. Ask the QA Engineer to locate the task’s supporting evidence and explain the remaining checks before it becomes Done. In the rehearsal, compare the revised task dates with the work package so a local change does not leave the wider schedule unexplained.

• Tasks In Flight — Tasks in progress or review, with assignee, due date and effort visible for coordination.
• Task Board by Status — Task cards grouped by delivery state, including Blocked work that needs attention.
• Blocked Tasks — Assignments whose progress has stopped and needs an owner-led resolution.

Use task delivery and recorded time and raise concerns through issue triage and verification.