| Page Properties |
|---|
Status | | Status |
|---|
| colour | Yellow |
|---|
| title | PROPOSAL / DRAFT |
|---|
|
|
|---|
Contributing Team | Marco Morales , Andy Pethan |
|---|
Earlier Discovery | Teams v2 Blended Project Proposal |
|---|
Linked Initiatives | N/A |
|---|
Overview | This is a meta collection of proposed initiatives to transform and level up the Teams experience on Open edX to better support social, group, and project learning. Each initiative will have its own detailed product requirements page eventually. |
|---|
|
...
| Expand |
|---|
| title | Show Milestone Details |
|---|
|
Milestone 1a: Teams Infrastructure ModernizationUnderstand the changes necessary to move the Teams Django App in edx-platform out to its own MFE, rebuilding and supporting existing functionality with modern platform practices, all as we reduce the size of the edx-platform Core! Metrics: Development speed & Core reduction
Milestone 1b: Support for LTI Apps within TeamsUpdates to the Teams API to facilitate the ability to plug in other team applications beyond just discussion. Examples include live audio and video chat, social networking app integrations, collaborative document apps, diagram/sketching apps, and other tools that support live and async remote collaboration. As part of this, explore different tiers of controls that allow or disable groups of apps (such as allowing instructors to remove the entire category of live video tools from a large MOOC, or a team manager locking in a limited set of apps that the team can focus around control over team apps / tools linked in to a given team). Should consider how LTI might facilitate many more integrations as well as part of this effort. Metrics: Platform extensibility (including breadth and depth of partner commitment to build upon it) & Team engagement / usage (professor adoption/approach and student buy-in/usage).
Milestone 1c: Teams Discussion UpdatesSupport new Discussions MFE in teams and streamline the UI for team discussions to encourage more frequent usage. The new MFE is a purely infrastructural improvement to be able to abandon the older code-base and invest new changes in the active code. The UI change addresses how the hierarchy of post-reply-comment is a bit bloated for a team and likely to reduce spontaneous conversation. A visual reformatting with the same back-end structure, “channel”-”message”-”thread”, could give teams a Slack-like UI for conversations that are still organized, yet easier to display from a team home view and embed in a future sidebar. Channel names could be prefixed with “teamshortname-” to simplify views that integrated chat from multiple teams of the same student. All teams can default to have a “teamshortname-general” channel to make it easy for new teams to begin using discussions. After the MFE integration, the rest of this milestone requires no changes to the data model. Metrics: Student engagement with teams and team discussions
Milestone 1d: In-Context Teams SidebarThis effort involves bringing team conversation as an optionally pervasive secondary sidebar in the learning MFE. Whether for team assignments, or more open conversation, teams could have ongoing conversations alongside a course. Team discussion updates (above) would make it easier to flip between multiple channels of conversation in the sidebar and engage in quick posts. Metrics: Course student engagement (learner session duration, time in course, learner outcomes)
Initial exemplar application extensions to the LTI Apps milestone above, this would allow teams to join on demand video calls, schedule future team conversations, or whatever other potential tools are possible for Zoom / BBB. The Zoom work could extend from the existing LTI Pro integration. Both video apps would have a primary UI component within the teams view, but we have an opportunity to integrate teams apps into the in-context course view via the Teams sidebar (above). Metrics: Student course engagement
|
...
| Expand |
|---|
|
This allows users to invite off-platform friends via a link to join an edX course and be auto-joined to a specific team. Within the homepage of a team, any member of that team can generate an invite link to send to friends via other communication platforms. When opened, the user is led through the sign-up process, auto-added to the course, and then auto-added to the team. This way, new users can begin with instant community (of their real friends). Metrics: proportion of invited users, retention of invited users
Milestone 2b: Language & Location TeamsThis action would allow all cohort users to automatically be placed into teams based around preferred language or global location (based on user settings). To ensure appropriately-sized teams, team formation could happen near the course start date, and then new students could be automatically added to the relevant teams. This gets all users initiated in their first team(s) so they can default to having community. Metrics: usage of teams, course engagement
Milestone 2c: Discussions: Introduction Post-TypeA feature-enriched type of discussion post that makes it easier for professors to add an introduction experience to courses and easier for students to connect with peers. The post gets pinned to the top of the discussion posts, each student gets exactly one reply (and the professor can visualize who has/has not replied), and anyone can comment on the student replies to say a short welcome. Professors can embed the intro post within the context of the course as a block so students know that it exists and is graded (participation). Student retention rates (early in the course and throughout)
Milestone 2d: Intro Post - Teams IntegrationWhen viewing each student reply in an introduction post, the viewing student can also see a list of the posting student's teams. The list allows the viewer to request to join any of the open/semi-private groups. This way, students who share mutual interests can find each other’s teams in the course and connect with each other, via teams, for future communication. Student retention rates (early in the course and throughout), use of teams chat in courses with/without intros and this integration
|
...
Initiative 3
...
Support for learners to invite their friends to learn with them in a course would help increase social learning among existing connections, increasing retention and engagement. Here, students could invite groups of students together and form a private social team / group in the teams experience. This builds on some of the items in the modernization and introduction areas above.
...
Platform Level Teams + Discussions
This initiative is meant to explore the value of augmenting the Teams + Discussions applications (given their interdependence) to function as platform level applications to support community discussions at the platform / site level.
Metrics: Platform learner retention
...
Initiatives 5+ - Others coming soon, draft in progress
Named Release
| Expand |
|---|
|
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. |
...