HKSM

A shared set of entry criteria a team uses to judge whether a user-centered backlog item is understood, valuable, and detailed enough to begin implementation.

Key Points

• Team-owned checklist that defines when a backlog item is ready to pull into execution.
• Applied to user-focused items (e.g., user stories) before commitment in sprint planning.
• Common elements include clear description and acceptance criteria, known value and priority, identified dependencies/risks, sizing/estimate, and testability.
• Improves flow and quality by preventing unclear or incomplete work from entering the sprint.

Example

Before sprint planning, the team reviews the story "As a customer, I can reset my password." It meets the DoR: the user value is stated, acceptance criteria list success and failure scenarios, UX mockups are attached, the dependency on the email service is resolved, the story is estimated and small enough for one sprint, and test data needs are noted. The team pulls it into the sprint.

PMP Example Question

During sprint planning, a story lacks acceptance criteria and has an unresolved dependency on a third-party API. Which practice should the team use to decide whether to include this item in the sprint?

1. Definition of Done
2. Definition of Ready
3. Product roadmap
4. Sprint retrospective action items

Correct Answer: B — Definition of Ready

Explanation: The Definition of Ready sets entry criteria for pulling work into a sprint; it ensures items are clear and feasible. The Definition of Done describes completion/exit criteria.