Epic Hypothesis Statement

An agile Epic is a body of work that can be broken down into specific tasks (called user stories) based on the needs/requests of customers or end-users. Epics are an important practice for agile and DevOps teams.

Funnel Entry Date	<The date that the epic entered the funnel.>
Epic Name	<A short name for the epic.>
Epic Owner	<Name of the epic owner.>
Epic Description	<An elevator pitch (value statement) that describes the epic in a clear and concise way.> For <customers> who <do something> the <solution> is a <something – the ‘how’> that <provides this value> unlike <competitor, current solution or non-existing solution> our solution <does something better — the ‘why’>
Business Outcomes	<The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.>
Leading Indicators	<The early measures that will help predict the business outcome hypothesis. For more on this topic, see the Innovation Accounting advanced topic article.>
Size	1 sprint , assume 10 people in 1 team . S   -  100 days M  -  200 days L   -  400 days
Priority	Items that are highly able to work with less constraints should mark as highest
Non-functional Requirements(NFRs)	<Nonfunctional requirements (NFRs) associated with the epic.>
Dependencies	<Any dependencies or prerequisites required for the completion of the Epic.> Dependency #1 Dependency #2 Dependency #3
Risk	<Any potential risks or obstacles that may impact the completion of the Epic.> Risk #1 Risk #2 Risk #3
Constraints	Please mark keywords in epic description why this is not working