The epic is the top level task item that defines a shippable feature or main theme to a group of work. This ticket should define from a top level, what the feature is intended to do, how it will look for the user and give enough information that further user journey stories can be written from it.

Epic Name

This is a short title for the epic.

Should be short enough to be easily glanced at amongst many other epics

Product Owner
Summary Also a title used in other parts of JIRA but should also not be too long  
Issue Type Epic  
Due Date Define only if necessarily  
Reporter This is ordinarily the product owner themselves although on occasions can be a stakeholder  
Story Points A relative number that sizes the tasks amongst other epics. This is to give a relative estimate of time and complexity to complete the task. Team
Business Value

Also a relative number amongst other epics but defines a relative value to the business.

This relative value includes user value as a users value is valuable to a business...

Product Owner

Initially the task requires at least a brief but then later will be filled in to include top level user stories, acceptance criteria, wireframes and eventually designs.


This is a short one liner that give anyone a high understanding of the feature requirement.

User Stories

Completed in their expected format;
As a ... <who the benefit is aimed at>
I want to... <what the beneficiary will do>
So that ...<the benefit>

Acceptance Criteria

A list of what the app must do, for example "User is able to connect the app to Chromecast" and "User is able to watch the stream on their TV via Chromecast"


Files are uploaded to the JIRA ticket as either PDF or JPG showing all frames that relate to this epic


The completed designs are uploaded to the JIRA ticket as either PDF or JPG showing all frames that relate to this epic and can be compared against for testing as well as giving the developers a clear understanding of what they are building.