Admin — Story Standards
Define the Definition of Ready and Definition of Done criteria applied to all Stories, and configure mandatory fields for story creation.
Story Definition of Ready
Criteria a Story must meet before it can be pulled into a sprint. Common items:
- Title and description written (As a / I want / So that)
- Acceptance criteria defined (at least 2 items)
- Story points estimated
- Dependencies identified
- No outstanding questions
Story Definition of Done
Criteria a Story must meet before it can be moved to Done. Common items:
- Code written and peer-reviewed (if applicable)
- All acceptance criteria verified
- No blocking bugs introduced
- Tested in a staging or test environment
- PO has accepted the Story
Mandatory fields
Configure which Story fields are required before saving. Mandatory fields prevent Stories from being saved without key information — useful for enforcing estimation before sprint planning.
Story templates
Define default description templates for each Story type (User Story, Bug, Spike). Templates pre-populate the description field when a new Story of that type is created, reducing blank-page friction.