PART 1

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

 Lessburn 3rd party contractor is currently providing several data services to Gazelle: Curating data for monthly project and tradeshow updates and sourcing expansion events for the AI. The TaskForce team India is already doing similar data curation work.

Value to Customers & Users

Internal users will have a closer control over the work and more long term stability

Value to Lightcast

To move more data creation in house.

Target User Role/Client/Client Category

Gazelle data team

Delivery Mechanism

Shared google doc sheet that gets updated weekly

Success Criteria & Metrics

Providing the same quality and speed of delivery as Lessburn

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.

Only the sourcing of expansion events is part of this epic, NO project or tradeshow work

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

• provide a test data set of one week of events sourced by TaskForce India and compare to Lessburn delivery

• after adjustments / review, evaluate when the TaskForce India team would have capacity to take over the work permanently

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.