Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following criteria should be met before a story is presented to the team for backlog review.

Need

  • User or system roles and restrictions are defined.

  • User intent is explicit.

  • Business outcome is clear.

    • The story clearly articulates the value to the user, or unlocks downstream technical opportunity or reduces future product/development risk. 

  • The story has been reviewed and accepted by the usergroup. 

  • The story priority has been accepted by the usergroup.

...

  • Workflow / UI expectations or assumptions are stated.

  • Fall-back, negative and alternative scenario flows are defined in addition to core flow, including example data.

  • Possible related functionality or behaviour that is out of scope is explicitly defined.

  • Necessary acceptance criteria are defined.

  • Acceptance criteria sufficiently reflect story intent and constraints, that the solution design must consider.

...