PART 1

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

As I client I want to leverage Lightcast updated areas across the various products as soon as they are available. I also need to make sure all products update are the same cadence.

Value to Customers & Users

This is primarily a significant internal process improvement - however, clients will benefit from more efficient Geo updates by seeing them in the tools faster and the engineering teams will be able to build other cool things in the time saved.

Value to Lightcast

Decouple the GIS build process from Analyst's area definitions so we can get new Geo areas out as soon as they are made available. This will improve time to delivery of new GIS areas and remove a challenging dependency chain between Micro and Analyst that occurs every datarun.

Target User Role/Client/Client Category

All clients

Delivery Mechanism

GIS API - build process improvement

Success Criteria & Metrics

Definition of Done: Have a useable script that works around our current process, so we can update the GIS API independently from Analyst.

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.