Navigation Section
Resource Calendars
– Project PASS PMP
Purpose
This document outlines when team members and key resources are available during the project.
It ensures:
- Schedule feasibility
- Workload balancing
- Alignment with milestone delivery
- Transparency around constraints
This file supports:
Resource Availability by Week
| Resource | Role | Week 1 | Week 2 | Week 3 | Week 4 | Notes |
|---|---|---|---|---|---|---|
| Sponsor | Sponsor | ✅ | ✅ | 🔲 | 🔲 | Hands-off after planning |
| PM | Project Manager | ✅ | ✅ | ✅ | ✅ | Full availability |
| Content Dev | Contributor | 🔲 | ✅ | ✅ | ✅ | Starts post-baseline |
| Reviewer | QA/SME | 🔲 | 🔲 | ✅ | ✅ | Reviews lessons + glossary |
| Case Writer | Contributor | 🔲 | 🔲 | 🔲 | ✅ | Single deliverable |
| Tech Lead | Publishing | 🔲 | 🔲 | ✅ | ✅ | Quartz setup + deploy |
Sprint-Based View (Alternative Format)
If managing work in sprints, structure availability like this:
| Sprint | Resource | Committed Hours | Availability Issues |
|---|---|---|---|
| Sprint 1 | PM, Sponsor | 10 hrs / 10 hrs | None |
| Sprint 2 | Content Dev | 15 hrs | Review delay possible |
| Sprint 3 | Reviewer, Tech Lead | 8 hrs, 6 hrs | Glossary revision cycle |
| Sprint 4 | All roles | 100% | Final QA and publish |
Capacity Conflict Resolution
If a resource is overbooked or unavailable:
- The PM will reallocate or defer work
- The Training Plan may be used to onboard backups
- Notes will be added to the Team Charter
Related Artifacts
Approval
| Name | Role | Signature | Date |
|---|---|---|---|
| PM | Scheduler | ||
| Sponsor | Approver |
📌 Use this calendar to validate who is available, when they’re available, and how their effort fits into the delivery plan. All estimates and schedules rely on this file for reality-checking availability.