{Early Draft}

@David Beauchamp @Thomas Worden → you’re tagged on here because I suspect you’d be involved in the final plan here, but there’s not yet any work to do unless you’re curious. Scraping these 14 files is probably fairly light work

PART 1

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

(from pendo) Education:  “I really need filters that help me better serve our students who are studying on F-1 visas who need reports that filter for employers who have a history of sponsoring H-1B Visas”

Community: As a director of an immigrant serving organization, I want to know what industries in my region are attracting H-1B candidates and are obtaining H-1Bs to support my immigrant population. I want to be able to connect those candidates to industries and organizations that are likely to support sponsorship.

TBD: there are additional visas available at the same source

• H-2A (temporary agriculture)

• H-2B (temporary nonagriculture)

Value to Customers & Users

• Provides insight into the immigrant workforce that is not readily available in the tool

• Connects Lightcast data directly to data that I’m pulling from external sources via normalization to make customer’s job easier

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 

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? 

• Pull the data from https://www.uscis.gov/tools/reports-and-studies/h-1b-employer-data-hub/h-1b-employer-data-hub-files on an annual basis (like we do with IPEDS) (@David Beauchamp )

• Normalize the data against the our companies (@Thomas Worden ) (and perhaps against our industry coding?)

• Determine where to build the data into reports (TBD: @Michael Griebling (Deactivated) / @Jennifer (Deactivated) / @Caleb Paul )

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.