Please include:

• Overview: 1-2 sentences that describe the project

• Problem: 1-2 sentences that describe the primary user problem, challenge or barrier

• Use cases: As a [course author author/instructor/learner], I need to be able to [do something] because/in order to [achieve a specific outcome].

• Discovery approach: What questions would you ask to explore solutions to this problem?

Any relevant background information about the Initiative. What key pieces of information are important for newcomers to understand about the nature of the problem or pain point, the current user experience, etc. Please use the following format:

Milestone 1: [Title]

• [1-2 sentence abstract. Include key user stories if appropriate]

• [Impact metric]

• [Link to Epic where it may exist in GH, jira, etc]

First Named Release to include this initiative. Alphabetical named releases are generally cut in early April and early October. Based on the removal date, what named release would be the first without this code? Please reach out to the Build Test Release working group (#wg-build-test-release in Slack) if you're not sure. Use the letter, if you're not sure of the name.

Recognizing that many Initiatives evolve incrementally, please include a brief scope of the Initiative timeline. Please include a target Named Release, with contingencies if necessary.