Agile Requirements
Capture user stories in the form of:
As a <user role/type> I want <some action/ feature/ goal>, so that < benefits from/ reasons for it>
Capture acceptance tests in the form of:
GIVEN (some context/precondition) [ AND (some more context/precondition) ...]
WHEN (event/action performed by user)
THEN (expected outcome - what should happen to satisfy user requirement from the user story statement above).
See https://www.infoq.com/articles/standardize-requirements-scrum
Comments