United Profiles Dataset
Created Date | Jun 8, 2023 |
---|---|
Target PI | PI4 |
Target Release |
|
Jira Epic | |
Document Status | Draft |
Epic Owner | @john.miner (Deactivated) |
Stakeholder | @John Pernsteiner @Matt McNair |
Engineering Team(s) Involved | Documents |
PART 1
Problem
With a renewed Cognism contract, we have additional sources of profile data that are not used in our products. By combining our various data sources there is the opportunity to compare and create profiles that have more depth than today.
Value to Customers & Users
Profiles with more reliable and accessible information
Value to Lightcast
Profiles with data aggregated from multiple sources - adds more validity to a profile
A single data source that represent Lightcast’s best-in-class profile dataset
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
Identified needs for ingesting Cognism data and any issues associated with the processing
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 |
---|---|---|
|
|
|