Definition of Ready
The “Definition of Ready” is a guideline of what detail stories should have to be ready for development. Stories should be well described and easily understood.
Scrum.org’s “Walking through a Definition of Ready” suggests using the I.N.V.E.S.T. criteria. We suggest using the following template that encompasses much of I.N.V.E.S.T.
As a USER,
Artifacts
Out of Scope
NFRs
Dev Notes
ACsGIVEN state
| The user story details the value of the story → Why we are doing this.
Defining what is out of scope keeps the work small.
Considerations around implementation. These considerations are negotiable.
Acceptance Criteria define what needs to be done. The cases are written in a Gherkin-like syntax. Use images and nest cases. These cases should be testable.
|
Example Story: Add a promotion to the checkout
As a customer,
I want to add a promotion to the cart
So that I spend less money on my order
Artifacts
Out of Scope
Adding a promotion on the cart page
Invalid promotions
Removing promotions
NFRs
Make sure we cycle auth tokens every year.
Dev Notes
While not supported right now, it’s suggested we send user credentials to validate the promotion code.
The pricing library will need to be updated to support promotions
The promotion component will be reused on the cart page
ACs
GIVEN the checkout page has a promotion area in the order summary:
WHEN a user enters a valid promotion code and hits
Apply, THENA spinner will be shown while the promotion is validated.
The apply button will be disabled.
The promotion code input will be disabled.
WHEN the promotion has been validated, THEN
the promotion name will be shown
the amount of the promotion will be shown
the total price will be updated
“Apply a promotion” will be changed to “Applied promotion”
WHEN the promotion is invalid, THEN provide an error message: