ops-capacity-plan

Per-person utilization forecasting aggregates current issue assignments, sprint commitments, and calendar availability to compute allocated hours and utilization rates for sprint planning. It consolidates planned work and meeting loads into a clear capacity plan.

Capacity planning quantifies per-person workload and surfaces resource gaps by analyzing team headcount against upcoming project commitments. It produces a capacity plan with gap analysis per project to show whether planned initiatives fit available capacity.

Yes, Linear issue assignments and sprint commitments can be consumed to calculate team capacity. The forecasting process pulls issues from Linear alongside calendar availability to include meetings, holidays, and out-of-office time in utilization computations.

Deciding between hiring, reprioritizing, or adjusting timelines relies on scenario-based recommendations generated from workload aggregation and bottleneck identification. The capacity plan outputs prioritized actions like hire, outsource, or deprioritize based on identified resource gaps.

You should run a capacity plan before quarterly roadmap planning sessions to verify whether planned initiatives fit available capacity. It analyzes workload, upcoming projects, and constraints like budget or hiring timelines to recommend scope changes or hiring.

Yes, capacity planning applies directly to engineering and operations teams assessing workload for sprints or quarterly roadmaps. It turns scattered issue assignments, meeting loads, and planned work into structured recommendations and scenarios.