HKSM

A structured technique used in SBOK to define and apply objective, product-focused criteria for assembling a cross-functional, self-organizing Scrum Team. It balances skills, availability, and collaboration qualities to ensure the team can deliver value each sprint.

Key Points

• Used during team formation and refresh to guide who joins the Scrum Team.
• Prioritizes cross-functional, T-shaped skills and the ability to collaborate.
• Targets a small, stable team size to maximize communication and focus.
• Emphasizes dedicated availability over part-time allocation.
• Includes soft skills, agile mindset, and readiness to be self-organizing.
• Considers domain, technology, compliance, and time-zone constraints.

Purpose of Analysis

This technique ensures the selected team can deliver the product vision and meet sprint goals without relying on heavy handoffs. It helps align staffing decisions with backlog needs, Definition of Done coverage, and real capacity rather than titles or seniority. It is most useful in Initiate or when scaling or re-forming teams between releases.

Method Steps

1. Clarify product vision and high-level epics to understand capability needs.
2. Define must-have vs nice-to-have criteria: skills, experience, certifications, and soft skills.
3. Assess cross-functionality by mapping backlog work types to required competencies.
4. Check candidate availability and dedication to avoid over-allocation and context switching.
5. Balance the team for size, diversity, and T-shaped skill coverage; confirm DoD and compliance needs are covered.
6. Validate collaboration fit: communication habits, openness, and willingness to self-organize.
7. Confirm logistics: co-location or plan for distributed practices, tools, and time-zone overlaps.
8. Document the selection rationale, onboarding plan, and any training or coaching gaps.
9. Review with Product Owner and Scrum Master; invite team input and adjust as needed.

Inputs Needed

• Project vision statement and high-level product roadmap.
• Epic-level product backlog and anticipated work types.
• Skills inventory and resource pool profiles.
• Availability calendars and allocation constraints.
• Quality, security, and regulatory requirements that influence team skills.
• Organizational policies on location, budget, and tooling.

Outputs Produced

• Scrum Team roster with confirmed roles: Product Owner, Scrum Master, Developers.
• Skills coverage matrix showing cross-functional capability and gaps.
• Initial team capacity baseline and availability notes.
• Onboarding and enablement plan, including training or coaching needs.
• Logistics setup: workspace or remote collaboration plan and tool access.

Interpretation Tips

• Optimize for team effectiveness, not individual brilliance or job titles.
• Prefer dedicated members over a larger number of part-time contributors.
• Focus on T-shaped profiles to reduce handoffs and increase flow.
• Include diverse perspectives to improve innovation and risk detection.
• Expect to iterate on composition as the backlog and context evolve.

Example

An organization plans a new product with epics in payments, reporting, and user management. The Product Owner and Scrum Master apply criteria: small team size, cross-functionality across backend, frontend, testing, and DevOps, and at least one member experienced in PCI compliance. Candidates are screened for availability to dedicate full-time, collaborative behavior, and willingness to pair. A 7-person team is formed, a skills matrix reveals a test automation gap, and a 2-week onboarding plan with coaching is scheduled.

Pitfalls

• Picking members by title or seniority instead of capability and collaboration.
• Forming an oversized team to chase speed, which often reduces throughput.
• Assigning members to multiple teams, causing context switching and delays.
• Ignoring soft skills and agile mindset, leading to handoffs and silos.
• Overfitting to the first release and neglecting adaptability for future work.
• Underestimating distributed-team needs for time-zone overlap and tooling.

PMP/SCRUM Example Question

During Initiate, a Scrum Master and Product Owner are assembling a new Scrum Team. Which criterion best reflects effective use of Scrum Team Selection Criteria?

1. Select the highest-rated individual performers regardless of collaboration history.
2. Choose a cross-functional group with full-time availability that covers Definition of Done needs.
3. Fill roles strictly by job titles to ensure clear handoffs between functions.
4. Maximize headcount to increase velocity in the first sprint.

Correct Answer: B — Choose a cross-functional group with full-time availability that covers Definition of Done needs.

Explanation: The technique emphasizes cross-functionality, dedication, and quality coverage. Titles, individual ratings, and oversized teams do not ensure effective delivery.