Epic Title
Description
[Provide a concise and clear description of the epic. What problem does it solve? What is its purpose?]
Goals
- [List the high-level goals or objectives of the epic]
User Stories
- [List the user stories associated with this epic]
- [Each user story should be a concise description of a specific functionality or feature desired by the user]
Acceptance Criteria
- [Define the criteria that must be met for the epic to be considered complete]
- [Clearly specify the expected outcomes or behavior]
Dependencies
- [Identify any dependencies that need to be resolved before starting work on the epic]
- [This could include other epics, user stories, or external factors]
Resources and Documentation
- [Provide links or references to any relevant documentation, design files, or external resources]
Notes
- [Add any additional notes or comments that are relevant to the epic]
- [This could include clarifications, suggestions, or any other information]
Timeline and Scheduling
- [Specify the estimated start and end dates for the epic]
- [Include any planned milestones or deadlines]
Team Members
- [List the team members who will be responsible for working on this epic]
- [Include their roles or responsibilities]
Labels
- [Add relevant labels to categorize the epic (e.g., priority, feature type)]
Related Epics or Issues
- [Provide links or references to any related epics, issues, or tasks]