You are on page 1of 3

Epic Brief: [Epic]

Epic Description
Epic Description
Title, ID Give the Epic a brief title that will be used in many
discussions. The title should be easy to remember and bring
an appropriate image to mind when used.
Epic Owner The person responsible for realizing the value or benefit
Epic Delivery The person responsible for delivering the Epic
Business Describe how the work supports the Investment Theme and
Objective addresses a business capability.

Value Statement
[Draft a problem statement or a product positioning statement to clarify the current situation]

Problem Statement
The problem of
The impact is
A successful
solution would

Product Positioning Statement

Our Product

Business Capability, User Journey or other Business Context Diagram
[Attach a simple visual model showing users interacting with business capabilities]

Feature/Deliverabl Description/Benefit

User Description

1 Confidential and proprietary 3/27/2017

Epic Brief: [Epic]

[List key risks, dependencies, assumptions and timing]

Risks Description
Business Risk
Technical Risks

Assumptions/Timin Description

High Level Architectural View

[A simple visual model showing conceptual architecture]

Item Estimate/ Budget
Time Critical
Risk Reduction
Planning Duration
Build Duration
Release Target

This Epic Brief template supports the definition and flow of Epics until they are delivered or killed.
This document is progressively updated throughout the flow of the initiative. Epic Brief Flow is
summarized here. Details of the flow are found in the Product Owner Training Guide.

1. Strategic Alignment: Investment Alignment/Prioritization

2 Confidential and proprietary 3/27/2017

Epic Brief: [Epic]
a. Epic Owner completes the Epic Description and Overview Statements
b. Portfolio Management Team (PMT) validates alignment with strategy and decides
whether to authorize further investment to elaborate the Epic Brief
c. Program Team (PGT) prioritizes and maintains the Epic on the Epic Roadmap per the
PMT guidance
2. Demand Planning: Investment Validation
a. Epic Owner records Features and Personas sections
b. PGT pulls the Epic in priority order. Solution Architect works with the Epic Owner to
complete the Constraints section.
c. PMT decides whether to authorize further investment and move to Release
3. Demand Planning: Release Targeting
a. PGT & EO elaborates and defines features sufficiently to target a release on the Epic
Roadmap (Rapid Estimation); EO & PGT completes the Planning section
b. PMT decides whether to authorize further investment for Agile Teams to perform
Detailed Planning
4. Detailed Planning: Release Viability
a. With support from the EO and PGT, Agile Teams write and plan stories sufficiently for
effective Release Planning.
b. Release Manager facilitates release planning and ensures suitable plans are
prepared; EO and PGT collaborate closely in detailed planning
c. PMT decides whether planning and value is sufficient to authorize Epic for further
investment for Agile Teams to Develop and Test the Epic
5. Develop and Test
a. EO & PGT provide support and guidance to the Agile Teams to ensure value of the
Epic is delivered; Epic Owner participates in Demos to review and accepts both
Stories and Features
b. PMT monitors progress to support teams, generate options and make continue,
change or kill decisions.

3 Confidential and proprietary 3/27/2017