Capacity Management
Munera tracks real-time utilisation for every engineer and uses this data to prevent overloading, plan sprints accurately, and forecast delivery timelines.
How utilisation is calculated
Each engineer has a weekly capacity (hours available per week, default 40). Munera calculates a real-time utilisation score:
Utilisation % = (sum of estimated hours on active assignments) ÷ (weekly capacity hours) × 100The utilisation score is colour-coded throughout the interface:
| Colour | Range | Meaning |
|---|---|---|
| Green | 0–79% | Engineer has capacity for more work |
| Yellow | 80–100% | Engineer is near capacity — assign with care |
| Red | >100% | Engineer is overloaded — assignments may be delayed |
Setting engineer capacity
Engineers can update their own capacity under Profile → Capacity. Managers and admins can edit any engineer's capacity from Team → [Engineer name] → Edit Profile.
Capacity can be adjusted temporarily — for example, when an engineer is on partial leave or on-call rotation.
Workload dashboard
Navigate to Analytics → Workload to see the team-wide utilisation heatmap. This page shows:
- Current assignment count per engineer
- Utilisation percentage (colour coded)
- Overdue task count per engineer
- Estimated hours remaining on active work
Sprint capacity planning
When building a sprint, Munera shows projected capacity automatically — the total estimated hours of tasks in the sprint versus the total available hours across the team for the sprint period.
Predictive analytics
Munera's ML models provide three types of forward-looking capacity insight:
Sprint capacity forecast
Predicted deliverable story points based on team availability and historical velocity using Holt-Winters time series models.
Delivery date estimates
Confidence-interval estimates for when specific tasks will complete, accounting for current load and complexity.
Burnout risk detection
Rule-based scoring that identifies engineers showing signs of sustained overutilisation before it becomes a problem.
Skill gap analysis
Compares skills required by open tasks against skills available across the team, and flags coverage gaps.
Workload snapshots
Celery Beat automatically takes daily workload snapshots. These are stored for historical trend analysis and power the velocity and throughput charts in the Analytics section. Snapshots run at midnight UTC by default and can be configured via WORKLOAD_SNAPSHOT_CRON in your environment file.