HKSM

A structured set of measurable attributes and weights used to evaluate and choose among alternatives such as vendors, tools, or team candidates in a Scrum context. It enables transparent, objective, and value-aligned decisions that support the product vision and project constraints.

Key Points

• Tool and technique to compare options using predefined, weighted criteria.
• Applied in SBOK mainly during Initiate (e.g., forming the Scrum Team, selecting vendors/tools) and reused as needed in later phases.
• Scrum Master facilitates the process; the Product Owner or sponsoring organization makes the decision based on results.
• Produces a documented scoring matrix, a ranked shortlist, and a clear decision rationale.
• Criteria align with product vision, value, risk, cost, compliance, and timelines.
• Criteria and weights are agreed before evaluating candidates to reduce bias.

Purpose of Analysis

The technique focuses stakeholders on what matters most and how to measure it. It turns subjective preferences into a repeatable, auditable process that supports quick, defendable choices.

In Scrumstudy SBOK, this helps teams select the right people, vendors, and tools early, reducing rework and risk while maintaining transparency with stakeholders.

Method Steps

1. Clarify the decision goal and constraints (e.g., budget ceiling, time-to-market, compliance needs).
2. List viable candidates or options to be evaluated.
3. Define measurable criteria aligned to the product vision, value, risk, and quality expectations.
4. Assign weights to criteria to reflect importance; validate with key stakeholders.
5. Create a scoring scale (e.g., 1–5) with clear descriptions for each level.
6. Independently score each candidate; then review and normalize scores as a group.
7. Aggregate weighted scores to produce a ranked list and shortlist.
8. Discuss trade-offs, run sensitivity checks on weights, and confirm the selection.
9. Document the decision, assumptions, and any follow-up actions (e.g., due diligence, pilot).

Inputs Needed

• Project vision and business value goals.
• Constraints: budget, schedule, compliance, security, and organizational policies.
• Candidate information: proposals, resumes, case studies, references, tool evaluations, or demos.
• Risk considerations and nonfunctional requirements (e.g., performance, supportability).
• Procurement or HR guidelines if external vendors or staffing are involved.

Outputs Produced

• Weighted scoring matrix with individual and consolidated scores.
• Ranked shortlist and a recommended choice.
• Decision log entry including rationale, assumptions, and constraints.
• Follow-up plan such as pilot evaluation, contract negotiation, or onboarding steps.

Interpretation Tips

• Focus on gaps that materially affect value, quality, or risk, not minor score differences.
• Use sensitivity analysis: adjust weights to see if rankings change under plausible scenarios.
• Set minimum thresholds for critical criteria (e.g., compliance) that cannot be traded off.
• Invite subject-matter experts to validate scores where the team lacks deep expertise.
• Escalate if no candidate meets mandatory thresholds; do not force a selection.

Example

The Product Owner needs a third-party API provider for a key feature targeted in the first release. The Scrum Master facilitates a workshop to build criteria: reliability, security certifications, latency, pricing, support SLAs, and integration effort. Weights emphasize reliability and security.

Three vendors are scored 1–5 against each criterion, weights are applied, and totals are ranked. The top vendor is selected, contingent on a short pilot spike in the next sprint to validate latency and SDK fit. The team records the decision and assumptions in the decision log.

Pitfalls

• Vague or non-measurable criteria that invite bias.
• Weights decided after seeing proposals, which skews outcomes.
• Overemphasis on cost at the expense of risk and quality.
• Ignoring mandatory compliance or security thresholds.
• Too many criteria causing scoring fatigue and inconsistent results.
• Failure to document rationale, making the decision hard to defend later.

PMP/SCRUM Example Question

The team must choose a vendor during Initiate to provide a critical API. To apply the Selection Criteria technique effectively, what should the Scrum Master facilitate?

1. An unweighted list of desired features followed by choosing the lowest-cost bidder.
2. A weighted scoring matrix with predefined criteria aligned to the product vision, scored by a cross-functional group to produce a ranked shortlist.
3. A quick brainstorming session ending with a simple majority vote.
4. A demo day, then select the vendor that presents the fastest prototype.

Correct Answer: B — A weighted scoring matrix aligned with the vision and scored by a cross-functional group to produce a ranked shortlist.

Explanation: Selection Criteria in SBOK is a structured, weighted evaluation method. It emphasizes objective, transparent scoring over cost-only decisions, voting, or demos without measurable criteria.