HKSM

Short, user-centered statements that describe a need and the value it delivers. They break scope into small, testable items that guide prioritization, delivery, and acceptance.

Key Points

• Small, value-focused scope items written from a user or stakeholder perspective.
• Common format: As a [role], I want [need] so that [benefit].
• Include acceptance criteria that make the story testable and unambiguous.
• Sized for a single iteration where possible; may be split from epics or features.
• Follow INVEST qualities: Independent, Negotiable, Valuable, Estimable, Small, Testable.
• Live in a product backlog and connect to the scope structure (epics → features → stories).
• Serve as a basis for estimation, prioritization, development, and validation.

Purpose

Translate stakeholder needs into clear, actionable scope items that focus on delivered value. Enable collaborative planning, right-sized work, and objective acceptance. Provide a flexible structure for evolving requirements while maintaining traceability to outcomes.

How to Create

• Identify user roles or personas and clarify the problem or job to be done.
• Draft the story using the role–need–benefit structure to emphasize value.
• Add acceptance criteria, often in Given–When–Then style, to define observable outcomes.
• Refine with stakeholders to remove ambiguity and confirm scope boundaries.
• Split large items into smaller, independent slices that deliver end-to-end value.
• Estimate relative size (e.g., story points) and note dependencies or assumptions.
• Attach supporting artifacts such as mockups, data rules, and nonfunctional constraints.
• Review against INVEST and update based on feedback and discovery.

How to Use

• Prioritize in the backlog to sequence delivery by value, risk, and dependencies.
• Plan iterations or releases by selecting ready stories within team capacity.
• Guide design, development, and testing through clearly stated acceptance criteria.
• Validate scope by demonstrating completed stories to stakeholders for acceptance.
• Trace stories to epics, features, and business objectives for alignment and reporting.
• Support forecasting and progress tracking via velocity and cumulative flow.
• Manage changes by updating criteria, splitting, or reprioritizing as understanding evolves.
• Integrate with a WBS or requirements register in hybrid or predictive environments.

Ownership & Update Cadence

• Primary owner: Product Owner or business representative accountable for content and priority.
• Contributors: Delivery team refines details, estimates, and technical considerations.
• Cadence: Continuous refinement; formal review during backlog refinement and before each iteration.
• Change control: Lightweight in adaptive approaches; governed baselines in predictive or hybrid contexts.

Example

As a frequent traveler, I want to save my payment method so that I can check out faster.

• Acceptance criteria: Given a valid card, when I save it, then it appears in my wallet with the last four digits masked.
• Acceptance criteria: Given an expired card, when I try to save it, then I see an error explaining the issue.
• Acceptance criteria: Given a saved card, when I check out, then I can select it and complete payment without re-entering details.

As a project manager, I want a dashboard filter by team so that I can view relevant metrics.

• Acceptance criteria: Given team selections, when I apply filters, then charts and tables update within two seconds.

PMP Example Question

A team is structuring scope for an upcoming release and needs small, testable items that capture user value and can be prioritized in the backlog. What should they produce?

1. A detailed work breakdown structure dictionary.
2. User stories with acceptance criteria.
3. A risk register with response strategies.
4. A responsibility assignment matrix.

Correct Answer: B — User stories with acceptance criteria.

Explanation: User stories express user-focused scope in small, testable units and live in the backlog. Acceptance criteria enable clear development and validation.