📘 Story Creation Guidelines – Advanced Analytics
Purpose
A Story represents an actionable requirement that contributes to the delivery of a Feature. It should be clear, and achievable within a sprint.
Ownership
Stories are created by the developer responsible for the project, with input from stakeholders and team members to ensure alignment and completeness.
Scope & Granularity
- Each Story should represent a couple of days of work.
- It must be small enough to complete within a single sprint.
Naming Convention
- The title should begin with an identifier of the overall project, followed by a descriptive title of the work to be done.
Linkage
- Every Story must be linked to a parent Feature.
- Dependencies between Stories should be documented using predecessor and successor links when priority or dependency is not clear in the order of the backlog.
Status Tracking
| Status | Description |
|---|---|
| New | Awaiting triage or prioritization. |
| Active | Currently being worked on. |
| Resolved | Not currently used |
| Closed | All acceptance criteria are met; no further action needed. |
| Removed | No longer relevant or replaced by another item. |
Acceptance Criteria
Each Story must include specific and binary acceptance criteria:
- Clearly define what success looks like.
- Should allow for a clear determination of whether the criteria are met or unmet.
Story Types
| Type | Description |
|---|---|
| User Story | Defined at the start of the project. |
| Missed Requirement | Added after project start due to oversight. |
| Enhancement | Adds value but was not defined during planning. |
| Story Carryover | Stories not completed in their original sprint. |
| Support | Resolves issues or provides assistance for production infrastructure. |
| Bug | Fixes issues in the current code base. |
| Feedback | Captures observations of a solution that do not require immediate action; stored in the project backlog and moved to the Product Enhancements epic if not addressed before production. |
Story Points
- 1 point = 1 hour of work.
- Points must be defined before development begins.
- If adjustments are needed mid-project:
- Enter the original estimate in the “Original Estimate” field.
- Update the current estimate in the “Story Points” field.
Priority
- The order of Stories in the backlog reflects their priority.
- Stories at the top of the backlog should be completed first.