This Resource Calendars Software Development document shows the individual availability calendars for all seven ProjectAdm team members across the full 13.5-month project duration — recording working hours, PTO, public holidays by country, and sprint-level allocation percentages. Eduardo Montes used these calendars to calculate accurate sprint capacities and prevent the common failure of planning full-velocity sprints during periods when team availability was actually reduced by 20–30%.

What Are Resource Calendars?

Resource Calendars are a PMBOK 8 output in the Planning Performance Domain that specify the working days and hours, non-working periods, and availability of each project resource. They are inputs to schedule development, resource allocation, and capacity planning. For human resources, resource calendars capture national holidays (which vary by country on international teams), planned PTO, and part-time allocation periods. For equipment and cloud resources, they capture maintenance windows and service availability constraints. Resource calendars prevent the common planning error of assuming 100% availability for all resources in all sprints.

What This Resource Calendars Software Development Includes

The ProjectAdm Resource Calendars workbook contains individual calendar sheets for each of the 7 team members:

• Eduardo Montes Calendar — Location: Brazil; 100% allocation Jan 15, 2025 – Feb 28, 2026; Brazilian public holidays applied (9 days across project); PTO: 10 days (Jul 21–25 — annual leave, pre-approved Sprint 13 planning session rescheduled); Conference attendance: PM Summit São Paulo (Nov 3–4 — pre-approved, async coverage by Henry Douglas for 2 standups)
• Henry Douglas Calendar — Location: US (EST); 80% allocation throughout; US public holidays applied (8 days across project); PTO: 5 days (Aug 25–29 — Sprint 17 PO sessions rescheduled to async Notion updates); Product Owner availability: minimum 4 hrs/sprint for backlog refinement maintained throughout all 28 sprints
• Marcus Webb Calendar — Location: Brazil; 100% allocation; Brazilian holidays applied; PTO: 5 days (Oct 20–24 — Sprint 21); No unplanned absences; on-call rotation for staging deployments: Friday afternoons (documented in Resource Management Plan)
• Julia Chen Calendar — Location: Brazil; 100% allocation; Brazilian holidays applied; PTO: 10 days (Jan 6–10, 2026 — Sprint 27 recess); Sprint 8–9: +10% overtime logged during ISS-003 Safari fix (compensated with 10 days extra PTO in Jan 2026); 0 unplanned absences
• Bruno Silva Calendar — Location: Brazil; 100% allocation; Brazilian holidays applied; Transitioned from prior project Jan 10, 2025 (5 days before kickoff — onboarding period); Sprint 15–17: temporarily 110% utilization during ISS-002 reallocation (compensated via sprint 18 reduced load)
• Camila Rocha Calendar — Location: Brazil; 80% allocation throughout (20% on other design work); Brazilian holidays applied; PTO: 5 days (Jul 14–18 — reduced Sprint 14 capacity by 5 story points); Sprint 23: allocation temporarily 100% for go-live UI final review
• Lucas Park Calendar — Location: Brazil; Variable: 60% standard, 100% during milestone acceptance weeks (Sprints 8, 14, 22, 28); Brazilian holidays applied; PTO: 10 days (Dec 22 – Jan 2 — Sprint 27/28 recess covered by pre-Sprint 26 QA completion); Part-time arrangement with HR pre-approved for project duration

How Eduardo Montes Used This Resource Calendars Software Development

Eduardo Montes loaded the Resource Calendars Software Development data into the Project Calendars workbook to calculate the actual story point capacity for each sprint. The combined view revealed that Sprint 14 had a 12% capacity reduction (Camila Rocha PTO + Corpus Christi holiday) — Eduardo reduced the sprint planning target from 42 SP to 38 SP. The team delivered 40 SP (5% above the reduced target), which was reported as a positive velocity result rather than a missed 42 SP target that would have appeared as a performance shortfall without calendar-based planning.

How to Use This Resource Calendars Software Development Document

When building your own Resource Calendars Software Development workbook, collect PTO plans from all team members before finalizing sprint capacity targets. The ProjectAdm approach of collecting all 7 calendars in January 2025 (at project kickoff) enabled accurate sprint capacity planning for all 28 sprints without mid-sprint surprises.

Download the Template and Deepen Your Knowledge

Ready to create your own resource calendars? Download the blank Resource Calendars Template (PMBOK 8).

• Download the Resource Calendars Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Resource Calendars in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning