API - Data Deployment Updates (Data Delivery)
Created Date | Apr 5, 2023 |
---|---|
Target PI | PI3 |
Target Release | |
Jira Epic | |
Document Status | Draft |
Epic Owner | @Andrew Brown (Deactivated) |
Stakeholder | @Nick Studt (Deactivated) |
Engineering Team(s) Involved | Data Delivery |
PART 1
Customer/User Job-to-be-Done or Problem
I want the latest Lightcast data/datarun as soon as it’s available.
Value to Customers & Users
Fast delivery of data updates for our clients.
Value to Lightcast
Config service updates to re-enable snowflake updates (this is necessary to keep the lights on)
Config service UI to allow datapro to move things from alpha/beta/general availability
Automate datarun deployments for agnitio, comp, IO, snowflake
Target User Role/Client/Client Category
Who are we building this for?
Delivery Mechanism
How will users receive the value?
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?
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
Effort Size Estimate |
---|
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.
Team | Effort Estimate (T-shirt sizes) | Jira Link |
---|---|---|
|
|
|