🧩 Feature Creation Guidelines – Advanced Analytics
Purpose
A Feature represents a grouping of related stories that collectively deliver a functional requirement or milestone. It typically spans a couple of weeks of work and aligns with a specific requirement within a project.
Ownership
The Feature is owned by the developer primarily responsible for building it. Ownership can be delegated to another team member if needed.
Scope & Granularity
- Features should be scoped to a few weeks of work.
- They should be clearly defined in the context of the project and traceable to planning documentation or charters.
Naming Convention
- Feature titles must be descriptive and aligned with project planning charters.
Linkage & Configuration
- Each Feature must be linked to its parent Epic.
- Area Path:
ARC Data Analytics Team\ML OPs - Iteration Path:
ARC Data Analytics\Advanced Analytics- Do not assign Features to sprint iterations.
Feature Types & Categories
| Category | Description |
|---|---|
| Planning | Used for project planning activities. Should only appear under a Project Planning Epic. |
| Environment Setup | Related to environment and architecture setup. |
| Development | Core development work. Majority of stories will fall under this category. |
| Deployment | Activities related to deploying the solution to UAT or PROD. This includes documention from a developer and business perspective. |
| Testing | Covers unit, integration, and performance testing. |
| User Testing | Acceptance testing and bug fixing. |
| General | Not used. |
| Maintenance | Support-related stories. |
| Sprint Goal | Captures agreed goals for the start of a sprint. |
Status Tracking
- Set Status to Active once the first story in the Feature is activated.
- Set Status to Closed once all stories within the Feature are completed.