Anna Hofmann·
Spotted my designer was double-booked in March and handed me a leveled resource plan to fix it
Creates an optimized resource allocation plan with capacity modeling, leveling, and bottleneck identification.
Resource Allocation Optimizer
You are a resource management specialist who optimizes team capacity across complex projects. Create a resource allocation plan for {{project_name}} running from {{start_date}} to {{end_date}}. The team consists of: {{team_composition}} (list roles and FTE availability). The project has {{project_phase_count}} major phases. Constraints include: {{constraints}}. Deliver: (1) A resource inventory with each person's role, skills, availability percentage, and cost rate, (2) A phase-by-phase resource assignment matrix showing who works on what and when, (3) A capacity vs. demand analysis for each role identifying overallocation and underutilization, (4) Resource leveling recommendations to resolve conflicts, (5) A resource histogram showing workload distribution over time, (6) Critical resource identification and backup/contingency plans, (7) A skills gap analysis for the project requirements, (8) Hiring/training recommendations if gaps exist, (9) A resource cost forecast by phase and month, (10) A resource reallocation trigger framework for when priorities shift. Present as actionable tables and recommendations.
Ergebnisse
# Resource Allocation Plan — Project Atlas (Mar 1 – Aug 31)
**Team:** 2 backend (1.0 FTE each), 1 frontend (0.8), 1 designer (0.5), 1 QA (0.6), 1 PM (0.4). **Phases:** Discovery, Build, Hardening. **Constraints:** designer shared with another project; QA ramps in May.
## Resource inventory
| Person | Role | Skills | Avail | Rate/day |
|--------|------|--------|-------|----------|
| Ben | Backend | API, DB | 100% | EUR 520 |
| Ada | Backend | Infra, API | 100% | EUR 540 |
| Kim | Frontend | React | 80% | EUR 480 |
| Tom | Design | UX/UI | 50% | EUR 460 |
| Sara | QA | E2E, perf | 60% | EUR 420 |
## Phase assignment
| Phase | Mar | Apr | May | Jun | Jul | Aug |
|-------|-----|-----|-----|-----|-----|-----|
| Discovery | Tom, PM | | | | | |
| Build | Ben, Ada, Kim | Ben, Ada, Kim | Ben, Ada, Kim | Ben, Kim | | |
| Hardening | | | Sara | Sara | Sara, Ada | Sara |
## Capacity vs demand
- **Overallocated:** Tom in March (also on Project Nova) — risk.
- **Underused:** Sara before May ramp.
## Leveling
Shift Tom's Atlas work to late March; pull QA test-planning forward (low effort, fills Sara's idle weeks).
**Critical resource:** Ada (only infra owner) — document her setup + cross-train Ben as backup. **Skills gap:** no dedicated perf tester → upskill Sara or contract 5 days. **Cost forecast:** peak burn April (~EUR 38k). **Reallocation trigger:** if Discovery slips >1 week, rebalance Build start.
Modell: Claude Sonnet 4
23 Likes8 SavesScore: 20
1 Kommentar
Sofia Almeida·
Saved me from another week of reactive firefighting.