7. RESOURCE PLANNING

Project Name: [Your Project Name]
Owner/Lead: [Your Name]
Created: [MM/DD/YYYY]
Status: [Planning / In Progress / On Hold / Completed]

Overview

This document defines team structure, skills requirements, budget allocation, and resource management strategies. It ensures the right people are in place at the right time with the necessary skills and budget.

Connections: Uses Sections 2 (Objectives), 5 (Timeline); Feeds into Sections 7 (Risks), 8 (Execution), 11 (Governance)

Team Composition

Core Team Structure

Extended Team

Skills Gap Analysis

Required Skills

Hiring Plan

Phase 1 (Weeks 1-2):

• Technical Lead (if not assigned)
• Backend Engineer #1

Phase 2 (Weeks 3-4):

• Frontend Engineer
• DevOps Engineer (part-time)

Phase 3 (Weeks 5-8):

• QA Engineer (part-time)
• Backend Engineer #2 (if needed)

Phase 4 (Weeks 9-10):

• Security Consultant (contract)
• Performance Engineer (if needed)

Budget Allocation

Personnel Costs

Infrastructure Costs

Tools & Services

Contingency

Total Budget

Vendor & Partner Dependencies

Mitigation Strategies:

• Identify backup vendors for critical services
• Negotiate SLAs with key vendors
• Maintain vendor relationship contacts

Onboarding Plan

New Team Member Onboarding Checklist

Week 1:

• Access to repositories and tools granted
• Read START-HERE.md and QUICK-START.md
• Review Section 1 (Executive Summary)
• Review Section 4 (Architecture)
• Development environment setup
• Meet with team members
• Attend sprint planning

Week 2:

• Complete first small task
• Code review process explained
• Testing standards reviewed
• Deployment process explained
• Shadow experienced team member

Week 3:

• Take ownership of feature
• Participate in code reviews
• Contribute to documentation
• Attend all ceremonies

Communication Channels

Reporting Lines

Steering Committee
    ↓
Project Lead
    ├── Technical Lead
    │   ├── Backend Engineers
    │   ├── Frontend Engineers
    │   └── DevOps Engineer
    ├── Product Manager
    │   └── Designer
    └── QA Engineer

Resource Constraints

Known Constraints:

• Budget limit: $[X]
• Team size limit: [X] people
• Timeline constraint: Launch by [Date]
• Skill availability: [Specific skills hard to find]
• Geographic constraints: [Remote/onsite requirements]

Mitigation:

• Prioritize critical roles first
• Use contractors for specialized skills
• Cross-train existing team members
• Adjust scope if resources unavailable

Capacity Planning

Team Capacity by Phase

Actions for High Utilization (>90%):

• Hire additional team members
• Reduce scope
• Extend timeline
• Increase contractor usage

Success Metrics

Resource Planning Success:

• Team fully staffed by Phase 2
• Budget within 10% of estimate
• No critical skill gaps
• Onboarding time under 2 weeks
• Team utilization 70-85%

Last Updated: [Date]
Next Review: [Date]
Owner: [Name]