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.
- Change Request Management
- Process
- Task execution
Task execution
Tasks show the work required to deliver a package. The board groups them by status; the package retains the governing scope, budget and review position. The Project Manager uses both records to decide whether the work is ready for a reviewer.
Step by step
-
Plan tasks Project Manager
Project Manager creates lines under the package, sets planned hours, priority and due date, and names an assignee where known.
- Set delivery lines and effort
- Updates Tasks, Work packages
-
Start delivery Delivery Contributor
Delivery Contributor moves a task from Backlog to in progress and records actual hours as work proceeds.
- Show active work and actual hours
- Updates Tasks
-
Handle blocked work Project Manager
A contributor marks a blocked task Blocked and explains the obstacle in its description. Project Manager checks whether the package scope or date must change.
- Expose schedule or scope risk
- Updates Tasks, Work packages
-
Check completed work Delivery Contributor
Work moves through in review to Done as the team verifies it. A completed task can record a completion date.
- Record finished work and evidence
- Updates Tasks, Record attachments
-
Reconcile the plan Project Manager
Project Manager compares task planned and actual hours with the package budget and impact assessment before package Review.
- Explain effort against scope
- Updates Tasks, Impact assessments, Work packages
Who does what
Roles and permissions- Project Manager
- Owns the task plan, Delivery Contributor records progress and Delivery Lead reviews effort across packages.
Set up Change Request Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.