...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Overview
…
Key Use Cases
…
As an Instructor, I
Deliverables
Stage 1
Stage 2
Users
Platform-Level Super User:
…
In Scope / Out of Scope
Based on the above use cases, we are breaking down on high-level scope as follows:
In Scope | Out of Scope |
MVP Specs
Features & Requirements
In order to realize this MVP, we believe the following features will be required. Refer to the following flow chart for more details:
Feature | Requirements |
Feature 1 | All users with Studio Home access have the ability to |
Feature 2 | Designated platform-level super users have the ability to do the following across the instance:
Designated org-level super users have the ability to do the following across the org:
All super user enabled.. Super users can.. Non-super users have the ability to…. |
Feature 3 | Content Authors can turn taxonomies (instance and org-levels) on/off at the course level. |
Feature 4 | Content Authors can… This includes:
Permissions… |
Feature 5 | Authors can … |
Feature behavior
X
Technical Open Questions
We anticipate the following to some of the key questions that we will need answered during technical discovery.
X
Successful Rollout: UI Considerations
We believe there is some risk in … We believe that organizations will need time to …. Therefore, we want to be conscious about how ….
We are proposing the following to help drive adoption:
New User Product Tour: X
Product & UX/UI FAQ
The following represent our Product view of key questions. However, we look to the UX/UI and technical teams to validate these as needed.
...
Q: How will ..
A:
Q: Decision on ..
A:
Future Direction
The following features are not part of the MVP but may be added during future development of this product. They are offered here only for consideration as MVP platform decisions are made that may impact future opportunities.
YYYY:
X
YYYY:
X
YYYY:
X
UI Examples
…