Planara
ENDE
Open app

Capacity planning

Net capacity, not headcount.

Five developers is not 200 hours a week. Planara subtracts holidays, vacations, meetings and a realistic productivity factor, then shows what’s genuinely left.

Open the appSee scheduling
  • Per team & per person
  • Offline holiday database
  • Day → quarter zoom

Where the hours actually go

Work schedules, per team and per person

Set working days and hours for a team, then override them for anyone part-time or on a different rhythm.

  • Mon–Sun working pattern
  • Hours per day
  • Per-member overrides

Public holidays, built in

Pick a country and optional region per team. The offline holiday database removes the right days, no manual calendar entry.

  • ISO country + region
  • Bundled, works offline
  • Different calendars per team

Vacations and company events

Individual time off and team-wide events come straight off available hours, so a planning week reflects who’s actually in.

  • Per-member vacations
  • Team or single-member events
  • Synced or entered by hand

A productivity baseline you can tune

Start from industry net-% standards per methodology and role, then nudge any individual up or down. Capacity stays honest about meetings and overhead.

  • Per methodology & role
  • Per-person offset
  • Recurring role reservations

Methodologies

Your way of working sets the baseline

Scrum & XP

Sprints, planning, stand-ups, reviews and retros carry real overhead, so net productive time runs lower. A Scrum developer plans around 75% net, a lead developer ~60%, while coordination-heavy roles like product owner and project manager land near 45–50%.

  • Ceremonies counted as overhead
  • Lower net % for coordination roles
  • XP sits a touch below Scrum

Kanban

A leaner, flow-based way of working means less ceremony, so the same people keep a few more points (developers around 80% net, testers ~72%), letting continuous-delivery teams plan a little tighter.

  • Least ceremony overhead
  • Highest developer net %
  • Built for steady flow

Waterfall

Phase-based work with stable plans keeps net % high for builders (~78% for developers) while project managers and product owners still reserve time for sign-offs and coordination.

  • Stable, phase-based plans
  • High builder net %
  • Coordination still reserved

No methodology

Choose “None” to skip net-% modelling entirely. The calendar then shows plain working days, handy for teams that track availability on a simple in/out basis.

  • Binary working-day basis
  • No productivity factor
  • Switch per team, anytime

Scrum · net productivity by role

Developer
75% net
Tester
70% net
Lead developer
60% net
Product owner
50% net
Project manager
45% net

See it

A heatmap you can read at a glance

Green is free, red is gone

Every cell is one person or team on one day or week. Zoom from a single day out to a whole quarter; hover any cell for the breakdown: holidays, time off, and what’s left.

  • Four zoom levels, day to quarter
  • Expand a team to its members
  • Today is always marked

At a glance

Granularity
Team & individual
Zoom
Day · Week · Month · Quarter
Holidays
Offline, by country & region
Productivity
Standards + per-person offset

Capacity questions

How is net capacity calculated?

Working hours for the day, minus holidays and time off, multiplied by a productivity percentage (an industry baseline plus any per-person offset), clamped to a sensible range.

Can two teams use different holidays?

Yes. Each team has its own country and optional region, so a plan can span Austria, Germany and beyond at once.

What are role reservations?

Recurring time a role owes elsewhere, like developers reserved for support. You can also cap how many people a reservation applies to.

See your team’s real hours

Add a team, pick a holiday calendar, and watch the heatmap fill in.

Open the app