LEARN. PRACTICE. GROW.Concept and mechanism
Refinement continuously splits and clarifies items to support upcoming decisions. An item should allow discussion of the user, need, benefit, and observable acceptance conditions. User stories are one possible technique; their format is not imposed by the Scrum Guide. Acceptance criteria describe results specific to an item. The Definition of Done establishes the quality state required for the Increment and still applies. Meeting a list of acceptance criteria does not authorize skipping tests or controls included in that definition. Developers performing the work are responsible for sizing it. The Product Owner helps clarify options and trade-offs without replacing that judgment with an estimate convenient for the deadline.
Guided application
A fictional story asks an operator to inspect a transfer result. Together, define how to distinguish received, rejected, and unknown states, which data they may inspect, and expected behavior when the source does not respond. Split an oversized request into a usable part that solves a real need while preserving applicable controls. Splitting only into interface, database, and tests can leave three deliveries with no independently observable value. An item still failing the Definition of Done returns to the backlog for future consideration and should not be presented as a completed Increment. A local readiness checklist may help, but should not become a bureaucratic barrier preventing learning or collaboration during the Sprint.
Item acceptance and Definition of Done have complementary functions.
Common pitfalls
Format treated as the goal; imposed estimates; unusable technical slices; quality traded away to close items.
Related topics: Goal, value, and accountability · Needs and discovery · Ordering and explicit trade-offs
Clarify the outcome and preserve shared quality.
Reference: Writing user stories · Scrum Guide November2020; EBM May2024; primary product practice reviewed 2026-09-30