Acceptance-Based Story

[ak-sep-tuh ns beys stawr-ee, stohr-ee]

Definition of Acceptance-Based Story

A Story whose Acceptance Criteria does not include a Time-Box; the Time an Acceptance-Based Story takes is a byproduct of getting to “Done.” 

See:

Time-Boxed Story, Time-Boxed Stories have their Acceptance Criteria (at least partially) defined by a time-box, and the actual Results produced are limited to what can be completed (using the Story’s Standard of...
Acceptance Criteria, The description of the objective criteria the Team will use to determine whether or not a Story achieves the Value it represents; the part of “Done” that is separate from...
Standard of Care, The Standard of Care is the part of “Done” that describes the objective criteria the Team uses to determine whether or not they used the prudence, caution, processes, and procedures...
Done A piece of work is “Done” when it satisfies the (pre-existing) agreement between Stakeholders and Developers about what it takes for the work to be complete; “Done” for a Story...

Examples

Acceptance-Based Stories are those that have their Doneness defined by explicit Acceptance Criteria, and the effort it takes to do them is a byproduct of getting to Done; non-Functional examples include ‘Release Buy an e-Ticket to the Production Server’ and ‘Install junit on all the Team’s machines’.

Functional Stories are Acceptance-Based Stories that are defined by an Acceptance Test, like ‘Get List of Flights from CUTLASS’ or ‘add new Passenger to existing Itinerary’.

StoryPoints(Story), for an Acceptance-Based Story, is a relative measure of Ideal Effort, which is the effort it would take to develop the Story (meet both the Acceptance and Doneness Criteria) if everything were as it should be.

External Sources

Acceptance-Based Stories and Ideal Effort

Cite This Term

"Acceptance-Based Story" ScrumDictionary.com. Accessed Apr 25, 2024. https://scrumdictionary.com/term/acceptance-based-story/.