User endUser stories and Bugs should meet the Definition of Ready before they can be pulled into a sprint for delivery.
...
Workflow / UI expectations or assumptions are stated.
Fall-back, negative and alternative flows are defined in addition to core flow.
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.
Constraints
Essential business rules and constraints are specified.
Functional or technical constraints are specified.
Known API parameters are defined
When the story meets the above criteria, it is ready to be discussed during backlog review.
During Backlog Review / Before Sprint Planning
Ready for Sprint Planning?
The following criteria are tested during backlog review.
Implementation Factors
The story is negotiable, describing the need rather than the solution. Lead Dev
The story is testable, with clear and measurable criteria. Test Lead
Necessary acceptance criteria are defined. Test Lead.
Scenario sub-issues are defined for the Story's related acceptance criteria. Product Owner
Acceptance criteria sufficiently reflect story intent and constraints. Product Owner
endpoints or parameters are specified.
Issue Management
The story or bug is represented by a Jira issue in the DCB project. Product Owner
The Story issue in the DCB project is linked to (defines) a Feature issue or corresponds to an explicitly defined Statement of Work priority. Product Owner
The Story issue in the DCB project is linked to related issues that may have (or have had) an influence in how the story is implemented. Product Owner
Scenario sub-issues are defined for the Story's related acceptance criteria.
Status title TBC Bug issues must be linked to (is related to) a Story or Scenario issue. Product Owner.
When the story meets the above criteria, it is ready to be discussed during backlog review.
Jira Status: DRAFT
...
During Backlog Review / Before Sprint Planning
Ready for Sprint Planning?
The following criteria are tested during backlog review.
The story is negotiable, describing the need rather than the solution. Lead Dev
The story is testable, with clear and measurable criteria. Test Lead
When a story meets the above criteria, it is considered to be a ready for Sprint Planning.
If a story does not meet the above criteria, it is returned to Product Owner for further elaboration.
If technical input is necessary, an investigation spike may be scoped with well-defined goals and outputs to support additional elaboration.
Jira Status: DRAFT → OPEN
...
During Sprint Planning
Ready for Development?
...