PART 1

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

The Scope of the user problem should be narrowed to the scope you are planning to solve in this phase of work. There may be other aspects you are aware of and plan to solve in the future. For now, put those in the Out of Scope section.

When I as a data pull customer (including former NOVA data pull customer) have issues with paying for or downloading and processing the full scope of a Postings set (including the BODY field), I want to consume a simplified data offering, so I can download and process the data in a time reasonable for the research I have set out to accomplish and my technical limitations, including hardware limitations. Similar use case for Data Feed customers.

Value to Customers & Users

In the JTBD framework, these are the “pains” and “gains” your solution will address. Other ways to think about it: What’s the rationale for doing this work? Why is it a high priority problem for your customers and how will our solution add value?

Data Feed and Data Pull customers have the option to receive a simplified version of the Postings feed which can greatly improve download speeds and processing time.

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 
Lightcast Sales is afforded the pricing (and upsell) opportunity that NOVA provided them (namely, without or with the posting text).

Target User Role/Client/Client Category

Who are we building this for?

Consumers of the Lightcast Data Feeds, in particular Standard - One Time Data Pull customers.

Delivery Mechanism

How will users receive the value?

Via the Lightcast Data Feed or Data Pull files.

Success Criteria & Metrics

How will you know you’ve completed the epic? How will you know if you’ve successfully addressed this problem? What usage goals do you have for these new features? How will you measure them?

A Fortnightly All - Basic (final name tbd) feed is added to the Data Feeds that is partitioned same as Fortnightly All.

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

What are you still looking to resolve?

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.