This Physical Virtual Resource Assignments Software Development document shows how Eduardo Montes formally assigned both human team members and virtual/physical technical resources to specific WBS packages and sprints for the ProjectAdm SaaS platform. This Excel register covers the complete resource assignment picture — from server instances and software licenses to team member sprint allocations — ensuring every resource was purposefully assigned, tracked, and released at the appropriate project phase.

What Are Physical and Virtual Resource Assignments?

Physical and Virtual Resource Assignments are a PMBOK 8 output in the Planning Performance Domain that document the formal assignment of physical resources (equipment, facilities, hardware) and virtual resources (cloud services, software licenses, APIs) to project work packages. Unlike team assignments (which cover human resources), this output focuses on the non-human resources that the project consumes. For software development projects, virtual resources — cloud infrastructure, SaaS tools, third-party APIs — are often the most significant non-labor cost drivers and must be tracked with the same rigor as physical equipment on infrastructure projects.

What This Physical Virtual Resource Assignments Software Development Includes

The ProjectAdm resource assignments register covers all assigned resources across human and technical categories:

• Human Resource Assignments — Eduardo Montes: PM/SM assigned to all 12 WBS packages (oversight), 100%; Henry Douglas: WBS 1.3, 1.4, 1.7, 1.10, 1.11 (PO oversight + Tech Lead), 80%; Marcus Webb: WBS 1.1, 1.2, 1.7, 1.8, 1.9, 1.10 (backend), 100%; Julia Chen: WBS 1.2, 1.3, 1.4, 1.5, 1.7, 1.11, 1.12 (frontend), 100%; Bruno Silva: WBS 1.3, 1.5, 1.6, 1.8 (fullstack), 100%; Camila Rocha: WBS 1.2, 1.3, 1.4, 1.12 (UI/UX), 80%; Lucas Park: all WBS packages (QA), 60%
• AWS Cloud Resource Assignments — EC2 Auto Scaling Group (us-east-1): assigned to WBS 1.1, active from Sprint 2; EC2 Auto Scaling Group (sa-east-1): assigned to WBS 1.1, active from Sprint 3 (secondary region); RDS MariaDB Multi-AZ: assigned to WBS 1.1, Sprint 2; S3 Backup Bucket: assigned to WBS 1.1, Sprint 2; CloudFront CDN: assigned to WBS 1.12, Sprint 26; WAF: assigned to WBS 1.1, Sprint 24 (pre-launch security)
• Third-Party API Assignments — Stripe API v2024: assigned to WBS 1.8, Sprint 5–28 (production from Sprint 8); PayPal API v2: assigned to WBS 1.8, Sprint 6–28; OpenAI API GPT-4o: assigned to WBS 1.10, Sprint 18–28; Google OAuth 2.0: assigned to WBS 1.2, Sprint 4–28; AWS SES (email): assigned to WBS 1.6, Sprint 10–28
• Software License Assignments — GitHub Teams: assigned to all WBS packages (version control), Sprint 1–28; Notion Pro: assigned to project documentation, Sprint 1–28; Figma Professional (Camila Rocha): assigned to WBS 1.2, 1.3, 1.4, 1.7, 1.12, Sprint 1–22; PHP-CS-Fixer: CI pipeline, Sprint 1–28; PHPUnit 10: assigned to all WBS packages (QA), Sprint 1–28
• Development Environment Assignments — Local dev: MacBook Pro M3 (Henry Douglas, Julia Chen, Camila Rocha); Windows 11 Dev (Marcus Webb, Bruno Silva, Lucas Park); Ubuntu 22.04 WSL2 (Eduardo Montes); Staging environment: AWS t3.medium (us-east-1), active Sprint 2–28; Production environment: AWS t3.large × 2 (us-east-1 + sa-east-1 active Sprint 28)
• Resource Release Schedule — Dev EC2 instances terminated March 1, 2026; Staging environment scaled down March 15, 2026; All software licenses transitioned to operational budget April 1, 2026; Figma license transferred to Camila Rocha's operational design pool April 1, 2026

How Eduardo Montes Used This Physical Virtual Resource Assignments Software Development

Eduardo Montes used the Physical Virtual Resource Assignments Software Development register to manage the AWS cost budget. By tracking which EC2 instances were assigned to which WBS packages and when, Marcus Webb could shut down development instances between sprints (Friday evening through Sunday), reducing the monthly AWS cost from a projected $1,400 to the actual $1,239 during development. The assignment log also made the resource release schedule at project closure straightforward — every resource had a documented owner and release date.

How to Use This Physical Virtual Resource Assignments Software Development Document

When building your own Physical Virtual Resource Assignments Software Development register, include the activation and deactivation dates for each cloud resource. Cloud costs accumulate whether or not resources are being actively used — the ProjectAdm approach of tracking assignment periods saved approximately $2,100 in unnecessary development environment costs over 13.5 months.

Download the Template and Deepen Your Knowledge

Ready to create your own resource assignments? Download the blank Physical Virtual Resource Assignments Template (PMBOK 8).

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