Sprint capacity planning
Five developers over a two-week sprint is not 400 hours. Planara starts from gross working hours, takes off public holidays, vacations and company events, then applies a productivity factor, so you commit to the net hours that really exist.
The formula
Take each person working days in the sprint multiplied by their hours per day. A developer on 8 hours across 10 working days brings 80 gross hours before anything is subtracted.
Public holidays for each team country and region come off automatically, and so do individual vacations and team-wide company events. A holiday in the sprint and a two-day vacation simply remove those hours.
Ceremonies, reviews and overhead mean nobody codes 100% of their day. Planara starts from an industry net-percent baseline per methodology and role, which you can nudge per person, so a Scrum developer plans around 75% net rather than the full clock.
Gross minus holidays, vacation and events, multiplied by productivity, is the net capacity you can safely commit. Plan sub-tasks against it and Planara never books time the team does not have.
From capacity to a plan
Every cell is one person on one day of the sprint, colored by the hours left after holidays and time off. Green is free, red is gone, so an overloaded sprint is obvious before it starts.
Give a sub-task its effort and the roles it needs, and the bar grows to fit the net capacity that is free. If someone takes vacation mid-sprint, the same work simply takes longer instead of pretending the hours exist.
Take gross working hours for the sprint (working days times hours per day, per person), subtract public holidays, vacations and company events, then multiply by a productivity factor. The result is the net hours the team can commit. Planara does every step for you.
Because headcount ignores holidays, vacations and the overhead of ceremonies and meetings. Five developers over two weeks look like 400 hours but rarely deliver that. Net capacity is what you can actually plan against.
Planara starts from an industry net-percent baseline per methodology and role (for example around 75% for a Scrum developer) and lets you offset any individual up or down, so the factor matches how your team really works.
Yes. Those hours are removed from the person net capacity, so their available cells drop and any task relying on them stretches to fit the hours that remain.
No. Planara runs entirely in your browser and stores everything locally. Open it and start planning your sprint capacity right away.
Add your team, pick a holiday calendar, and watch the net hours for the sprint fill in. No sign-up, right in the browser.