Short answer: Capacity planning asks how much time your people have. Resource planning asks which skills and roles upcoming work will need, and when. Resource allocation assigns specific people to specific work. They run in that order, and Portfolio by HeroCoders handles all three inside Jira.
The three terms get used interchangeably, in job titles, in tool listings and in planning meetings. That causes real problems: a team says it has "done capacity planning" when it has only assigned work, or a PMO buys a "resource planning" tool that can't tell them who is overbooked next week. Here's what each one means, how they fit together, and how to do each in Jira.
The three terms at a glance
What is capacity planning?
Capacity planning works out how much time your people actually have to give. It starts with working hours and working days, then subtracts what isn't available: public holidays, vacation and sick days. Compare the result with the work already booked, and you know who has room and who is overbooked.
Capacity is a supply-side number. It doesn't care what the work is, only how much time exists to do it.
Worked example: a team of five works 7 hours a day, 5 days a week. Over a four-week month that's 5 × 7 × 20 = 700 hours. One person takes a week of vacation (35 hours) and there's one public holiday for everyone (35 hours). Real capacity is 630 hours. If 680 hours of estimated work is already booked, the team is 50 hours over before anything new arrives.
That's the arithmetic. The hard part is keeping it current as estimates, dates and time off change every day, which is why most teams outgrow the spreadsheet.
What is resource planning?
Resource planning looks at demand instead of supply. Before you know exactly who will do the work, you describe what the work needs: which role, which skills, how many hours and over which dates. "We'll need a data engineer for about 60 hours in March" is a resource plan.
This matters most for portfolio leads and PMOs, because it's how you spot a shortage before a project starts. If three initiatives each need a senior Java developer in the same month and you have two, resource planning tells you now, not in week three of the sprint.
What is resource allocation?
Resource allocation is the decision: this person does this work, on these dates. It turns a resource plan into assignments and uses capacity to check they're realistic. Good allocation spreads work so nobody is overbooked and nobody is idle.
Allocation is the most visible of the three, which is why it often gets mistaken for the whole job. Assigning work without checking capacity is just hoping.
How the three fit together
Think of them as one loop:
- Capacity planning tells you how many hours each person and team has, after holidays and time off.
- Resource planning describes the demand coming up, by role and skill.
- Resource allocation matches the two: the right people, on the right work, within their capacity.
Then the loop repeats. Estimates change, someone books leave, a project slips, and capacity shifts. The teams that plan well don't do this once a quarter. They keep all three connected to the live work.
Can we plan resources and capacity in Jira?
Jira Premium and Enterprise include basic capacity planning, at team level in Jira Plans and as a per-person view. That's a reasonable starting point if you're already on those plans. Teams usually need more when they want capacity, roles and skills, time off and assignments in one place, or when they're on Jira Free or Standard.
Portfolio by HeroCoders, our PPM and capacity planning app for Jira, covers all three, and its capacity planning and portfolio views work on Jira Free and Standard as well as Premium and Enterprise.
Capacity planning with Portfolio by HeroCoders
The Capacity Planner shows each person's workload on a timeline, built from the estimates already on your Jira work items. You choose whether those come from time estimates or story points. Availability comes from working hours and days, holiday calendars per location and each person's vacation and sick days.
Workload is colour-coded, so overbooked, fully booked, partially booked and unbooked people stand out, and time off has its own colour. Build planners from groups, users, teams, roles or skills, group them by user, team, role or project, and view capacity by day, week or month. We cover time off in more detail in Bringing PTO Tracking into Your Jira Capacity Planner.
Resource planning with Portfolio by HeroCoders
In the Advanced edition, Resource requests let you plan future demand before anyone is assigned. Each request has an estimated time, start and end dates, an optional role and skills, and linked work items. Requests sit on the Capacity Planner timeline next to real bookings, so you see future demand against today's workload.
Roles and skills are set once and assigned to people or Jira groups, and you can filter the planner by them. For a walkthrough, read Better Resource Planning in Jira with Resource Requests.
Resource allocation with Portfolio by HeroCoders
When a resource request is ready, assign it: Portfolio lists the available people who have the required role or skills, and you pick one. Day to day, you allocate directly in the Capacity Planner by dragging bookings between people, resizing them or splitting them across days. Unplanned work items can be dragged onto someone's plan, and every change syncs straight back to Jira.
Capacity Alerts close the loop in the portfolio itself. Any work item assigned to someone who's overbooked gets flagged, and one click takes you to the capacity plan to rebalance it. If your Jira plan includes Rovo, you can also ask the Portfolio Insights Rovo agent whether someone with a given skill has time free next week.
Common mistakes
- Planning capacity without time off. A capacity number that ignores holidays and leave is optimistic by design.
- Allocating before planning demand. If you only assign work as it arrives, you'll find skill shortages when it's too late to hire or reshuffle.
- Planning resources by name only. Naming a person for work six months away locks in a guess. Plan by role and skill first, then allocate closer to the date.
- Treating the plan as a one-off. Capacity changes every time an estimate or a date does. Keep the plan connected to Jira so it updates with the work.
For the wider picture of how this fits into portfolio management, see Jira PPM (Project Portfolio Management): The Complete Guide.
FAQ
What's the difference between capacity planning and resource planning?
Capacity planning measures supply: how many hours people have after holidays and time off. Resource planning describes demand: which roles and skills future work will need, and when.
Is resource allocation the same as resource planning?
No. Resource planning describes the people and skills work will need. Resource allocation assigns named people to specific work on specific dates.
Which comes first, capacity planning or resource allocation?
Capacity planning. You need to know how much time each person has before you can allocate work to them without overbooking anyone.
How do you calculate team capacity?
Multiply working hours per day by working days in the period for each person, subtract holidays and time off, and add the results. Compare the total with the estimated work already booked.
Can you do capacity planning in Jira without Premium?
Yes, with an app. Portfolio by HeroCoders' capacity planning and portfolio views work on Jira Free, Standard, Premium and Enterprise.
Can Portfolio by HeroCoders plan by role and skill?
Yes. In the Advanced edition, resource requests capture the role, skills, hours and dates future work needs, and help you assign someone available with the right skills.
Plan capacity, demand and assignments in one place
Portfolio by HeroCoders connects all three in Jira: real capacity after time off, future demand by role and skill, and assignments that stay within what people can deliver.
