This list is intended to help the Product Owner and Scrum teams in planning and Documentation plan for new features.
Feature Summary (add links if other pages exist):
Feature Release Dates:
Platform | Y/N | Date |
---|---|---|
Saudi (Takamol) | ||
Open edX Named release | ||
edx.org |
...
Course Staff Support:
Student Support:
Open Source Contact:
Does this substantially change partner experience?
...
Should draft documentation be shared before release?
(If yes, provide link that will be shared with early users)
Doc Task (to be done concurrently with development) | Required? | If yes, JIRA Number |
---|---|---|
String/message review of UX plans | ||
Final string reviews in software | ||
Add Help links/tokens | ||
Student-facing documentation changes | ||
Course staff documentation changes - Studio | ||
Course staff documentation changes - Insights | ||
Course staff documentation changes - Instructor Dashboard | ||
Open Education XML documentation changes | ||
Researcher documentation changes - SQL/Mongo | ||
Researcher documentation changes - Events | ||
API documentation changes | ||
Configuration changes (e.g., feature flag) | ||
edx.org copy changes | ||
Include in Upcoming Features in Release Notesweekly release notes | ||
Evaluate DemoX Impact | ||
Evaluate edX101 Impact | ||
Evaluate Training Impact |
Rollout Task (after Customer Portal launchto be done at release) | Required? | If yes, JIRA Number |
---|---|---|
Include in Release NotesRoadmap Page Update | Partner Blog Post | |
Partners | ||
Open edX Blog PostInclude in Weekly Release Notes | ||
Partner Home Page Highlight (Dates)Blog Post | ||
Open edX Partner Home Page Highlight (Dates) | ||
Feature Page | ||
Webinar | ||
Demo (Engineering/Client/Prod Council) | ||
Internal Lunch and Learn/Q&A | ||
Open edX | ||
Include in next Open edX Named Release release notes | ||
Open edX Blog Post | ||
Open edX Home Page Highlight (Dates) | ||
For OSPRs, add to OS Hall of Fame |