...
| Info |
|---|
Where a role is identified for each statement, that role is those best placed to verify that the condition is satisfied, rather than being the role responsible for ensuring it is met. |
Before Backlog Review
| Info |
|---|
Distinguish:
|
Ready for Backlog Review?
The following criteria should be met before a story is presented to the team for backlog review.
Need
User 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.
Essential business rules and constraints are specified.The story has been reviewed and accepted by the usergroup.
The story priority has been accepted by the usergroup.
Expectations
Workflow / UI expectations or assumptions are stated.
Possible related functionality or behaviour that is out of scope is explicitly definedefined.
The story has been reviewed and accepted by the usergroup.
The story priority has been accepted by the usergroup.
Constraints
Essential business rules and constraints are specified.
Functional or technical constraints are specified.
API parameters are defined
When the story meets the above criteria, it is ready to be discussed during backlog review.
...