Review capacity pressure
Compare planned effort with available capacity. Discuss overload before committing more work to the team.
Resource Allocation
See where capacity goes before committing more work
Connect planned effort, team capacity, and project allocation. Find workload pressure and discuss priorities with the teams doing the work.
Resource Allocation
Team capacity and project focusEngineering capacity overview
4 teams · 23 contributors
- Available capacity
- 230 effort points
- Planned effort
- 236 effort points
- Teams above capacity
- 2 of 4 teams
| Team | Contributors | Capacity | Planned effort | Utilization | Status |
|---|---|---|---|---|---|
| Platform | 8 | 80 | 88 | 110% | Slightly overloaded |
| Payments | 6 | 60 | 54 | 90% | Balanced |
| Mobile | 5 | 50 | 66 | 132% | Overloaded |
| Developer Experience | 4 | 40 | 28 | 70% | Underutilized |
Switch between workload and project allocation to explore the planning view.
Capacity discussions
Make the next planning decision with context
See where effort is allocated
Review the share of effort assigned to each project and initiative. Check whether priorities match the work being planned.
Use connected planning data
Bring work tracking and contributor profiles into the conversation, using integrations such as Jira, Azure Boards, and AgileSpace.
What to review
Read workload and project focus together
A full team can still be spread across competing priorities. Review capacity alongside allocation to understand both pressure and focus.
- Resource utilization
- Compare assigned work with the capacity recorded for a contributor or team.
- Project allocation
- Understand how planned effort is split across projects and initiatives.
- Team capacity
- Review resource count, project load, and utilization by effort or item count.
- Allocation status
- Use underutilized, balanced, slightly overloaded, and overloaded states to focus the discussion.
From planning to delivery
Check the work behind the allocation
Bring the plan into the same conversation as activity patterns and delivery outcomes.
Inspect participation over time
Use Activity Heatmap to investigate how contribution and review activity are distributed.
Explore Activity Heatmap →Follow team performance
Read work distribution, rework, and delivery trends alongside capacity decisions.
Explore Team Performance →Common questions
Resource allocation questions
Need to discuss your team or technical setup? Contact us.
What does Resource Allocation show?
It brings together team capacity, planned effort, project allocation, and utilization status so leaders can discuss workload and priorities with the same information.
Which systems provide allocation data?
Oobeya uses connected work tracking systems, including Jira, Azure Boards, and AgileSpace, alongside contributor profiles. Available fields depend on your integrations and planning setup.
Can we inspect both teams and contributors?
Yes. Review team capacity and the contributor-level allocation behind it to understand where planned effort is assigned.
Does utilization measure developer productivity?
Utilization describes planned workload relative to available capacity. Interpret it alongside delivery, quality, role, leave, and support responsibilities when making planning decisions.
How should we respond to an overloaded status?
Check the underlying assignments and capacity records with the team. Review priorities, deadlines, and opportunities to rebalance work before changing commitments.
Where can we review setup requirements?
The Resource Allocation documentation covers configuration. Bring your planning tools, effort fields, and team structure to a walkthrough to discuss your setup.
See Oobeya in practice
Bring your capacity questions to the next review
Walk through resource allocation with your team structure, planning tools, and delivery priorities.