HKSM

An Organizational Resource Matrix is an enterprise-level catalog of people, skills, roles, availability, and locations used to staff and support Scrum Teams. In SBOK, it is used as an input when forming teams and balancing capacity across sprints and releases, and it is updated as assignments change.

Key Points

• Enterprise list of people, skills, and availability maintained for staffing Scrum Teams.
• Acts as an input for Form Scrum Team and capacity planning across sprints and releases.
• Updated as an output when team assignments, onboarding dates, or capacity change.
• Supports scaling by highlighting shared specialists, time zones, and cross-team constraints.
• Owned by an organizational function such as HR, PMO, or Scrum Guidance Body, with regular updates.
• Enables transparent, skills-based selection while respecting self-organization and team preferences.

Purpose

The matrix makes staffing decisions faster and more transparent by showing who is available, what skills they have, and when they can join. It helps the Product Owner and Scrum Master build cross-functional teams and forecast capacity for sprints and releases.

It also exposes constraints such as time zone gaps, required compliance training, or vendor contracts that might affect sprint planning, dependencies, or Definition of Done.

Key Terms & Clauses

• Role and skill tags - e.g., UX, QA automation, DevOps, domain SME.
• Proficiency level - novice, proficient, expert or a numeric scale.
• Allocation and availability - % FTE, start-end dates, known PTO or holidays.
• Location and time zone - to coordinate events and handoffs.
• Constraints - compliance needs, required tools access, contract limits, visa or security clearance.
• Owner and update cadence - who maintains it and how often it is refreshed.
• Data privacy - store only necessary information and follow company policy.

How to Develop/Evaluate

• Define a common skill taxonomy aligned to product and technology stacks.
• Gather data from HR systems, functional managers, and individuals; validate with the Scrum Guidance Body if applicable.
• Capture availability by sprint or by week, including planned PTO and partial allocations.
• Record constraints such as training, onboarding lead time, and tool access prerequisites.
• Version and date-stamp the matrix; set an update cycle (for example, biweekly).
• Evaluate quality using completeness, accuracy vs. actuals, timeliness of updates, and usability by team leads.

How to Use

• Initiate - Form Scrum Team: shortlist candidates to create a cross-functional team with the right skills and availability.
• Plan and Estimate - Plan Releases: estimate team capacity, spot skill gaps for upcoming epics and user stories, and plan onboarding.
• Implement - Scrum of Scrums: coordinate shared specialists across teams and reduce resource-based dependencies.
• Support Backlog Refinement: identify SMEs for spikes, architecture reviews, or acceptance criteria clarification.
• Continuous Improvement: use the matrix after retrospectives to request training or hire for recurring gaps.

Example Snippet

Simple illustration of entries you might keep:

• A. Lee - Backend/API - Proficient - 80% available from Sprint 4 - UTC-5 - Needs cloud access approved.
• B. Kumar - QA Automation - Expert - 50% available now - UTC+1 - Shared with Team Delta.
• C. Rivera - UX/Research - Proficient - 100% from Sprint 2 - UTC-8 - PTO next week.

Risks & Tips

• Risk: Stale data leads to overpromising capacity. Tip: time-box updates and audit against actual velocity.
• Risk: Treating the matrix as command-and-control. Tip: use it to inform choices, then let teams self-organize final selection.
• Risk: Single-point specialists create bottlenecks. Tip: schedule pairing and cross-training to build redundancy.
• Risk: Ignoring onboarding lead times. Tip: include access, hardware, and training dates in availability.
• Risk: Over-allocating people across teams. Tip: cap concurrent team assignments and visualize FTE limits.
• Risk: Time zone friction. Tip: prefer clusters with overlapping hours or adjust event times accordingly.

PMP/SCRUM Example Question

A new epic requires strong test automation skills next sprint, but your current Scrum Team lacks this capability. What should the Scrum Master do first?

1. Ask the team to split the epic into smaller stories and proceed without automation.
2. Escalate to leadership to assign any available tester immediately.
3. Consult the Organizational Resource Matrix to identify available automation expertise and plan onboarding.
4. Increase the sprint length to accommodate manual testing.

Correct Answer: C — Consult the Organizational Resource Matrix to identify available automation expertise and plan onboarding.

Explanation: The matrix is an input to forming or adjusting team capacity and skills. It enables a fact-based, timely staffing decision while supporting cross-functional coverage.