HKSM

A team-based way to discover and describe requirements and business-focused functional tests by capturing concrete, real-world examples instead of vague, abstract statements.

Key Points

• Stakeholders, product owners, developers, and testers collaborate to build a shared understanding.
• Concrete examples are turned into acceptance criteria and often automated tests.
• Using real cases reduces ambiguity, uncovers edge conditions, and cuts rework.
• Creates living documentation and commonly aligns with BDD and Given-When-Then formats.

Example

An e-commerce team must implement a returns policy. They workshop examples with the business: "Item returned within 30 days with receipt: full refund," "31-60 days: store credit," "After 60 days: no refund." These examples become the acceptance criteria and automated tests for the returns feature, ensuring everyone shares the same understanding of the rules.

PMP Example Question

On an agile project, stakeholders are frequently confused by abstract requirements for pricing discounts. What technique should the team use to clarify expectations and derive acceptance tests?

1. Specification By Example (SBE)
2. Critical Path Method (CPM)
3. Wideband Delphi
4. Earned Value Management (EVM)

Correct Answer: A — Specification By Example (SBE)

Explanation: SBE uses concrete, real-world examples to define requirements and acceptance tests, reducing ambiguity and aligning stakeholders.