This Project Team Assignments Software Development document shows how Eduardo Montes formally assigned all seven ProjectAdm team members to their specific roles, WBS packages, and sprint responsibilities — creating the RACI matrix, sprint assignment grid, and allocation tracking that governed who did what across 28 sprints and 13.5 months. This Excel workbook is the human resource companion to the Resource Management Plan, documenting actual assignments rather than planned policies.

What Are Project Team Assignments?

Project Team Assignments are a PMBOK 8 output in the Team Performance Domain that document the formal assignment of project team members to their roles and responsibilities. They confirm who is assigned to the project, what their role is, which work packages or activities they own, their allocation percentage, and their start and end dates on the project. Team assignments are the bridge between the Resource Management Plan (which defines how resources will be managed) and the actual human beings doing the work — they translate policy into practice and create the accountability structure that makes delivery possible.

What This Project Team Assignments Software Development Includes

The ProjectAdm Project Team Assignments workbook covers all assignment dimensions for the 7-person team:

• Team Assignment Summary (Sheet 1) — Eduardo Montes: PM/Scrum Master, 100%, Jan 15, 2025 – Feb 28, 2026, all 12 WBS packages (oversight); Henry Douglas: PO/Tech Lead/Co-Sponsor, 80%, same dates, WBS 1.1–1.12 (technical authority); Marcus Webb: Sr. Backend, 100%, WBS 1.1, 1.2, 1.7, 1.8, 1.9, 1.10; Julia Chen: Sr. Frontend, 100%, WBS 1.2, 1.3, 1.4, 1.5, 1.7, 1.11, 1.12; Bruno Silva: Fullstack, 100%, WBS 1.3, 1.5, 1.6, 1.8; Camila Rocha: UI/UX, 80%, WBS 1.2, 1.3, 1.4, 1.12; Lucas Park: QA, 60%, all WBS (QA oversight)
• RACI Matrix (Sheet 2) — 20 key project decisions with R/A/C/I assignments; highlights: Architecture decisions (R=Henry Douglas, A=Eduardo Montes); Sprint acceptance (R=Henry Douglas as PO, A=Eduardo Montes as SM); Production deployment (R=Marcus Webb, A=Henry Douglas, C=Eduardo Montes); Contingency release (R=Eduardo Montes, A=Henry Douglas + CCB)
• Sprint Assignment Grid (Sheet 3) — 28 sprints × 7 team members; each cell shows: primary WBS package focus for that team member in that sprint; story points committed; color-coded by WBS package; highlights: Sprint 15–17 Bruno Silva reassigned from WBS 1.5 (frontend) to WBS 1.10 (backend ISS-002 fix)
• Allocation Tracking (Sheet 4) — Monthly actual vs. planned allocation percentage per team member; all team members maintained allocation within ±5% of plan throughout; Lucas Park's 60% allocation was the most variable (40% in low-QA sprints, 80% in milestone acceptance sprints) — managed via pre-agreed flexible arrangement with HR
• Key Assignment Events — Sprint 15: Bruno Silva reallocated from WBS 1.5 to WBS 1.10 (ISS-002); Sprint 22: Camila Rocha allocation reduced to 60% (other design project started); Sprint 26: Lucas Park allocation increased to 100% (penetration test and final QA sprint); Sprint 28: All team at 100% for final go-live activities
• Team Assignment Closure — All assignments formally closed Feb 28, 2026; transition assignments documented (Marcus Webb, Bruno Silva → operations; Henry Douglas → CPO); performance evaluations completed and signed by Eduardo Montes for all 5 direct team members

How Eduardo Montes Used This Project Team Assignments Software Development

Eduardo Montes used the Sprint Assignment Grid in the Project Team Assignments Software Development workbook to plan the Bruno Silva reallocation during the ISS-002 crisis. The grid allowed him to see at a glance which WBS packages Bruno was assigned to in Sprints 15–17 and what the coverage impact would be of moving him to backend work — he could see that WBS 1.5 (Team + Collaboration) had Julia Chen as backup, making the reallocation low-risk. This visual assignment tool made a complex resource decision a 10-minute analysis rather than a 2-day discussion.

How to Use This Project Team Assignments Software Development Document

When building your own Project Team Assignments Software Development workbook, maintain the sprint assignment grid as a living document updated each sprint planning session. The ProjectAdm approach of color-coding assignments by WBS package made allocation changes visually obvious — you could see at a glance when a team member's focus was shifting and whether that shift was intentional.

Download the Template and Deepen Your Knowledge

Ready to create your own team assignments document? Download the blank Project Team Assignments Template (PMBOK 8).

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