Problem description

<Clearly define the issue or challenge the epic seeks to address, outlining the impact on users or the system>

Solution hypothesis

<Describe the high-level approach or plan for addressing the problem, focusing on how the proposed changes will resolve the issue>

Functional and non-functional requirements

<Specify the system’s capabilities and behaviors needed for the solution (functional), along with performance, security, and usability constraints (non-functional)>

Success criteria

<List the conditions that must be met for the epic to be considered complete and for the solution to be accepted by stakeholders>

Dependencies

<Identify other projects, teams, or tasks the epic relies on or is linked to, ensuring smooth execution and integration>