PART 1

Problem

• Customers ask and have requested the desire/need to know particular metrics about employees like:

  • Years of Experience (YOE)

  • Tenure (time with a company, time in a role)

Value to Customers & Users

• Additional data points to profiles that customers can leverage in their data gathering and analysis.

Value to Lightcast

• New value to our products and customers

• New data points that Analyst and other teams can use

Delivery Mechanism

• Profile dataset

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?

• % of Profiles that insights can be applied to.

Aspects that are out of scope (of this phase)

• Delivery via API

PART 2

Solution Description

• Questions and research about creating/calculating/storing metrics is completed

• YOE metric is started

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

• Test on a % of Profiles before applying to them all.

Risks

• Profiles are based on self-reported data so there will be outliers and questions of validity.

Open Questions

• How do we handle Profiles missing a start/end date for a role?

• Should we store this value in months versus years?

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.