👑 Epic Creation Guidelines – Advanced Analytics
Purpose
Epics represent large bodies of work that span weeks to months. They are used to capture either:
- A defined project with clear deliverables.
- A grouping of support activities that share a common theme or objective.
Ownership
Epics are created once the Advanced Analytics team has committed to a project. Ownership remains with the individual team member responsible for executing the work.
Scope
The scope of an Epic is documented externally and referenced within the Epic via a link to the project charter or objective document. This ensures clarity and traceability.
Naming Convention
Epic titles should:
- Clearly describe the project or initiative.
- End with one of the following tags to indicate the delivery stage:
POC(Proof of Concept)MVP(Minimal Viable Product)PDZ(Productionize)
Linkage
Where applicable, Epics should include links to:
- Successor or predecessor projects to support planning and dependency tracking. Supervisor to add lineage based on project planning.
Dates
- Target Date: When the team plans to execute the project.
- Start Date: When development activity begins.
Epic Types
Use the following Epic types to categorize work:
| Epic Type | Description |
|---|---|
| Project | A defined project with deliverables. |
| Project Planning | Planning activities for a defined project. Focused around projects that require a charter |
| Support Generic | A grouping of support activities. |
| Technical Debt | A grouping of technical debt items. |
🛠️ Support Generic Epics in Advanced Analytics Backlogs
| Support Epic Type | Description |
|---|---|
| Product Enhancements | A collection of features and feedback to enhance an existing product. Each enhancement should be scoped to less than one month of work. |
| Product Support | A collection of issues and bugs that need to be fixed in existing products. |
| Stakeholder Requests | Work to assist stakeholders that does not involve development of a specific product. |