HKSM

A structured consultation with Human Resources specialists to inform Scrum staffing, capability development, contracts, and compliance decisions. It is used when forming or scaling a Scrum Team, addressing talent gaps, planning onboarding and training, or resolving HR-related impediments. The outcome is practical recommendations and artifacts that support self-organizing teams while aligning with organizational policies.

Key Points

• Tool/technique that brings HR expertise into Scrum planning and decision-making.
• Applied during team formation, scaling, release planning, and when HR impediments arise.
• Focuses on skills, capacity, hiring or redeployment, onboarding, training, and compliance.
• Produces actionable recommendations, staffing options, calendars, and cost or policy constraints.
• Supports self-organization by informing decisions without dictating task assignments.
• Helps maintain stable, cross-functional teams and sustainable pace.

Purpose of Analysis

The purpose is to analyze people-related factors that affect delivery: availability, skills mix, ramp-up time, labor laws, contracts, and budget. This ensures the Product Owner and Scrum Master have clear, policy-aligned options for forming or adjusting the team and removing HR-related impediments.

It also validates that any staffing action preserves agility, team stability, and compliance with organizational and regional regulations.

Method Steps

• Request HR consultation and agree on the decision to be informed (e.g., add skills, replace role, onboard contractors).
• Share context: product vision, release roadmap, forecasted velocity, skills matrix, and time constraints.
• Review talent options: internal redeployment, hiring, contracting, or training and upskilling.
• Assess compliance and policy impacts: labor rules, security clearances, location and time zone constraints, budget bands.
• Estimate ramp-up: onboarding duration, access provisioning, and training lead times.
• Document recommendations with pros, cons, costs, and risks; identify any HR-related impediments.
• Agree on next steps: job postings, transfers, training schedule, start dates, and update Scrum artifacts.

Inputs Needed

• Product vision, release plan, and near-term product backlog priorities.
• Current team skills matrix, historical velocity, and capacity forecasts.
• Organizational HR policies, compensation bands, and hiring or vendor guidelines.
• Budget constraints, location or time zone requirements, and security or compliance needs.
• Onboarding checklist and lead times for access, tools, and environments.

Outputs Produced

• Staffing recommendation (internal moves, hire, contractor, or training).
• Onboarding and training plan with timelines and responsible parties.
• Resource calendar or start dates aligned to sprint boundaries when feasible.
• Draft job descriptions or requisitions and candidate sourcing plan.
• Cost and policy considerations, plus any HR-related risks for the impediment log.
• Updates to release planning assumptions and capacity forecasts.

Interpretation Tips

• Treat advice as input to decisions; keep task assignment within the Scrum Team.
• Prefer options that preserve team stability and cross-functionality.
• Balance short-term capacity needs with long-term capability building.
• Schedule onboarding to minimize mid-sprint disruption and knowledge loss.
• Confirm that recommendations comply with regional labor and security rules.

Example

A Scrum Team plans a release that adds complex deployment automation. The Scrum Master consults HR with the release timeline, skills matrix, and capacity forecast. HR proposes an internal DevOps transfer within two weeks, a 3-day onboarding plan, and a short contractor engagement for peak load, plus a training session for current developers. The Product Owner and team choose this blended approach and update the release plan and calendars.

Pitfalls

• Letting HR assign individuals to tasks, which undermines self-organization.
• Optimizing for utilization rather than flow and predictable delivery.
• Hiring late in the release without accounting for ramp-up time.
• Ignoring time zone and access constraints that delay onboarding.
• Over-rotating people across teams, reducing cohesion and velocity.
• Confusing advice with mandates, or bypassing compliance guidance entirely.

PMP/SCRUM Example Question

A Scrum Team lacks a critical security skill for a near-term epic. What should the Scrum Master do first to address the gap while protecting team autonomy and the release plan?

1. Ask HR to assign a security specialist to the team and define their tasks.
2. Consult HR for options and ramp-up times, then let the team decide the best approach.
3. Delay the epic until a full-time hire is found, regardless of release impact.
4. Have the Product Owner remove security-related backlog items from the scope.

Correct Answer: B — Consult HR for options and ramp-up times, then let the team decide the best approach.

Explanation: Expert advice from HR provides informed options and constraints, while the Scrum Team retains self-organization to choose how to fill the gap. The other options either remove the team's autonomy or damage scope and schedule without informed analysis.