PART 1

Customer/User Job-to-be-Done or Problem

Using a variety of data points about companies to identify the most relevant targets

Value to Customers & Users

Improved frontend experience to allow users to access the most relevant information faster

Value to Lightcast

Improve retention rates as existing clients have been waiting for beta launch, and higher return on sales/demos with unique user experiences around growth companies

Target User Role/Client/Client Category

Gazelle users

Delivery Mechanism

Gazelle software

Success Criteria & Metrics

The Gazelle Web Application is deployed new UX & design, with some updated Frontend functionality, and is available for clients' use.

The development & QA process are organized with best practices of continuous delivery, including unit testing, functional testing, staging & production deployments etc.

The next releases (2.1, 2.2, …) could be designed and delivered on top of the initial 2.0 release.

Aspects that are out of scope (of this phase)

What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.

PART 2

Solution Description

Early UX (wireframes or mockups)

<FigmaLink>

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, localization requirements, mobile requirements, accessibility requirements

Dependencies

Is there any work that must precede this? Feature work? Ops work? 

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

• Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]

  • If specific beta customers, will it be for a specific survey launch date or report availability date 

• How will this guide the rollout of individual stories in the epic?

• The rollout strategy should be discussed with CS, Marketing, and Sales.

• How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all

Risks

Focus on risks unique to this feature, not overall delivery/execution risks. 

Open Questions

Identify additional Frontend developer and QA resources in Lightcast or outside to speed up delivery

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.