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.
- Capacity Planning Dashboard
- Who it's for
- Digital product delivery teams
Digital product delivery teams
A digital product delivery team needs to discuss new assignments alongside work already in progress and fixes waiting for examination. Keep project commitments and work packages recognizable, then use the task board to follow the current delivery state. Capacity decisions become easier to explain when the team can point to the dated work and the evidence still needed.
How Capacity Planning Dashboard is set up for you
Owned assignments
Give each task a clear title, assignee and estimate within its work package. Check its dates against the person's other commitments before moving it into the current cycle.
Review work
Keep tasks in review visible alongside implementation work. The Project Manager can discuss the next handoff with the QA Engineer before treating the work as Done.
Issue follow-through
Raise concerns with severity and project context, then inspect the triage result. Leave fixed issues recognizable until the verification procedure has been completed.
Resource concerns
Record risks with probability, impact, ownership and mitigation. Bring those concerns into the capacity discussion when the next project request depends on the same people.
A digital product delivery team needs to discuss new assignments alongside work already in progress and fixes waiting for examination. Keep project commitments and work packages recognizable, then use the task board to follow the current delivery state. Capacity decisions become easier to explain when the team can point to the dated work and the evidence still needed.
Choose a delivery package with an extraction task and a review milestone. Agree the planning period and compare the developer's assignments with the weekly baseline. Follow the task into progress, record time and rehearse a fix that is ready for the QA Engineer to examine.
Include a returned delivery decision so the team practices explaining what evidence remains. Review the next period's tasks after the correction, keeping unfinished work in the capacity discussion. Agree the connection to any existing source-control or release tooling separately with its owner. Start with the planning and evidence handoffs the team can rehearse using an actual project.
Follow [task delivery and recorded time](/capacity-planning-dashboard/processes/task-to-time), then use [issue triage and verification](/capacity-planning-dashboard/processes/issue-triage) for the exception case.
Features to start with
Delivery exceptions
Give issues, overdue work and resource risks a clear owner before they change the delivery plan.
Team capacity
Use weekly capacity, role and practice alongside dated task demand when deciding who can take on work.
Work packages
Organize project work into owned delivery blocks with dates, hour budgets and visible task demand.
Roles on the team
- Admin
- Maintains user access and the organization and personnel records used to identify delivery work.
- Delivery Lead
- Owns capacity assumptions and authorizes the project scope the team is prepared to deliver.
- Project Manager
- Plans assignments and coordinates time, milestones and exception follow-through for delivery work.
- Developer
- Maintains assigned task progress, records work time and raises issues with supporting evidence.
- QA Engineer
- Examines fixes and delivery evidence, records verification outcomes and books time against assigned work.
Set up Capacity Planning Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.