HKSM

Short, structured statements that capture what a user needs and why, using a consistent template. They express requirements in simple, plain language to improve stakeholder communication and enable more reliable effort estimation by the team.

Key Points

• Follow a consistent template: As a [role], I want [capability], so that [benefit].
• Include clear acceptance criteria (often in Given-When-Then) to define done and testability.
• Keep stories small, independent, valuable, and estimable (INVEST).
• Serve as conversation starters between stakeholders and the team; details emerge through collaboration.

Example

As an online shopper, I want to reset my password so that I can regain access if I forget it. Acceptance criteria: Given I am on the login page, when I click "Forgot password?" and enter my registered email, then I receive a reset link; the link expires in 30 minutes; after resetting, I can log in with the new password.

PMP Example Question

Which artifact best captures small, user-centered requirements in the format "As a [role], I want [goal], so that [benefit]" to improve communication and estimation?

1. User stories
2. Use cases
3. WBS work packages
4. Requirements traceability matrix

Correct Answer: A - User stories

Explanation: User stories are short, structured statements of user needs that enhance collaboration and estimation, typically using the "As a... I want... so that..." format.