This Resource Requirements Software Development document shows how Eduardo Montes identified and documented the specific human, physical, and virtual resources required for each of the 12 WBS packages of the ProjectAdm SaaS platform. This Excel workbook bridges the Resource Breakdown Structure (taxonomy) and the Resource Management Plan (policies) by specifying what each work package actually needs — quantities, skills, tools, and timing — before any resources are formally assigned.

What Are Resource Requirements?

Resource Requirements are a PMBOK 8 output in the Planning Performance Domain that describe the types and quantities of resources needed for each activity or work package in the project. They are inputs to resource management planning, cost estimation, and schedule development. For software projects, resource requirements specify not just "a developer" but the skill level (senior vs. junior), the specific technology expertise (PHP, JavaScript, MariaDB), the expected allocation percentage, and the tools and infrastructure needed to support the work. Detailed resource requirements prevent the common planning mistake of treating all development resources as interchangeable.

What This Resource Requirements Software Development Includes

The ProjectAdm Resource Requirements workbook documents requirements for all 12 WBS packages:

• WBS 1.1 — Architecture + Infrastructure — Human: Henry Douglas (Tech Lead, AWS expertise, 40 hrs), Marcus Webb (Sr. Backend, AWS/Linux, 120 hrs); Technology: AWS account, Terraform or manual IAM setup, GitHub repo initialization; Skills required: AWS multi-region deployment, MariaDB RDS setup, Nginx configuration, CI/CD pipeline setup
• WBS 1.4 — Kanban Engine — Human: Julia Chen (Sr. Frontend, HTML5 Drag-and-Drop, 320 hrs), Henry Douglas (PO review, 20 hrs), Lucas Park (QA, 32 hrs); Technology: Safari 17 test device (iOS + macOS), Chrome/Firefox/Edge test environments; Skills required: HTML5 Drag-and-Drop API, JavaScript event handling, cross-browser compatibility, WCAG 2.1 AA, CSS performance optimization
• WBS 1.7 — Gantt Chart Module (CR-002) — Human: Marcus Webb (backend API, 60 hrs), Julia Chen (D3.js frontend, 40 hrs), Lucas Park (QA, 10 hrs), Camila Rocha (UI design, 8 hrs); Technology: D3.js library (v7), PDF generation library (TCPDF); Skills required: D3.js data visualization, recursive task dependency algorithm, SQL recursive CTEs (ISS-002 mitigation applied)
• WBS 1.8 — Billing + Subscriptions — Human: Marcus Webb (backend, 160 hrs), Bruno Silva (frontend billing UI, 80 hrs), Lucas Park (payment QA, 24 hrs); Technology: Stripe API v2024, PayPal API v2, Stripe test cards, PayPal sandbox; Skills required: PCI-DSS compliance, webhook idempotency (ISS-004 lesson), subscription lifecycle management, multi-currency support
• WBS 1.10 — AI Suggestions Engine — Human: Henry Douglas (product spec, 20 hrs), Marcus Webb (API integration + queuing, 200 hrs), Julia Chen (UI, 40 hrs), Lucas Park (QA, 40 hrs); Technology: OpenAI API (GPT-4o, $800/month cap), request queue implementation; Skills required: OpenAI API integration, rate limit management (ISS-001 mitigation), async PHP job processing, prompt engineering
• WBS 1.12 — Landing Page + Documentation — Human: Camila Rocha (design, 80 hrs), Julia Chen (HTML/CSS, 60 hrs), Eduardo Montes (content/PM, 40 hrs); Technology: AWS CloudFront CDN (activated Sprint 26), Google Analytics 4, SEO tooling; Skills required: responsive web design, SEO on-page optimization, technical writing (API documentation), Swagger/OpenAPI
• Cross-Package Requirements — All packages: GitHub Teams (version control), Notion (documentation), PHPUnit (testing); All backend packages: PHP 8.1, CodeIgniter 4.4.4, MariaDB 10.6; All frontend packages: WCAG 2.1 AA compliance check, cross-browser test suite

How Eduardo Montes Used This Resource Requirements Software Development

Eduardo Montes used the Resource Requirements Software Development document during the CR-002 impact assessment to quickly determine which team members and tools were needed for the Gantt chart module. The WBS 1.7 requirements section (Marcus Webb backend + Julia Chen D3.js + Lucas Park QA) provided the basis for the 110-hour effort estimate and $4,500 cost that was documented in the change request. Without a detailed requirements document, this analysis would have required a separate planning session; with it, the CR-002 cost estimate was produced in under an hour.

How to Use This Resource Requirements Software Development Document

When writing your own Resource Requirements Software Development document, specify the skill requirements with enough detail to distinguish between interchangeable and non-interchangeable resources. The ProjectAdm WBS 1.10 requirement of "OpenAI API integration experience" was important — it correctly identified Marcus Webb (not Bruno Silva) as the primary resource, based on prior API integration work on the Phoenix project.

Download the Template and Deepen Your Knowledge

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

• Download the Resource Requirements Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Resource Requirements 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