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.
- Sprint / Agile Board
- Features
- Team Capacity
Team Capacity
Team members hold a role, practice and weekly capacity.
OverviewMy Stories×
Sprint / Agile Board · Team Capacity
New
My Stories
Stories
| Story key | Title | Sprint scope | Priority | Status | Due date | |
|---|---|---|---|---|---|---|
| SK-558 | Backlog str-758 | SS-7941 | Low | Backlog | 20 Oct | |
| SK-708 | In progress str-331 | SS-9003 | Medium | In progress | 13 Oct | |
| SK-189 | In review str-392 | SS-8892 | High | In review | 08 Oct | |
| SK-593 | Blocked str-435 | SS-6089 | Critical | Blocked | 11 Oct | |
| SK-778 | Done str-386 | SS-2647 | Low | Done | 19 Oct |
6 of 6 records
SK-558Stories · STR-16294
LowTitleBacklog str-758
Sprint scopeSS-7941
StatusBacklog
Due date20 Oct
What you can do
People and capacity
Team members hold a role, practice and weekly capacity. Assigned story counts, assigned estimates, actual hours and logged hours appear on the team member record. A Delivery Lead can use those values alongside the sprint scope estimate to see whether an assignment is practical.
How the work is organized
- Starting record. Team members hold a role, practice and weekly capacity.
- Named owner. Delivery Lead checks allocation; Project Manager assigns stories; Team Member keeps work and time current.
- Current position. The active member record and assigned stories show whose planned load needs attention next. The Delivery Lead compares assigned estimates with weekly capacity before confirming a sprint scope, then checks actual hours after the work begins.
What to agree during setup
Set weekly capacity in a consistent unit and decide who maintains it when availability changes. Agree how the team uses practice and role when assigning work. Treat the capacity figures as a planning aid: the owner still decides whether a particular person has the skills and time for the stories in the scope.
Compare a member’s assigned estimate with weekly capacity before the Project Manager commits the scope. Check that the person is active and that the story’s assignee is current. Actual and logged hours help the Delivery Lead revisit the allocation after work begins; they are distinct from the planned estimate.
Check the handoff on an actual case
A sprint scope starts next week and its stories have been assigned to a developer whose estimated load is already high. The Delivery Lead compares the assigned estimate with weekly capacity, then moves a story to another active team member. The Project Manager checks the story owner and sprint scope again before the team starts work. Actual and logged hours can later show where the original estimate was low.
The Delivery Lead checks the active member’s weekly capacity and assigned estimate again after the move. The Project Manager confirms the new assignee and sprint scope on the story. Once time is logged, the lead compares actual effort with the earlier estimate to decide whether the remaining allocation still fits.
What your team sees
- My Stories — Assigned work a team member needs to advance.
- Stories In Flight — Current work across the delivery team.
Follow the work through
See sprint planning for the planning handoff and review and approval for the decision record. Begin with a small project in implementation, then compare the team’s results with the data model.
What it keeps track of
Data model- Team members
- Delivery staff with role, practice and weekly capacity.
- Stories
- Individual pieces of work assigned to a delivery team member.
- Sprint scopes
- Groupings of work inside a project.
- Time entries
- Hours booked by a team member against a task and project.
Who uses it
Permissions- Delivery Lead
- Checks allocation; Project Manager assigns stories; Team Member keeps work and time current.
Set up Sprint / Agile Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.