MoodleNet/Roadmap: Difference between revisions
Doug Belshaw (talk | contribs) No edit summary |
Doug Belshaw (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
---- | ---- | ||
[[File:tasty-cupcake.png|right|frameless|200px]] | |||
== Roadmap == | == Roadmap == | ||
| Line 7: | Line 9: | ||
'''''Note:''' this is a work in progress to create a high-level overview of the MoodleNet project. For more granular detail, please check out the [https://trello.com/b/wkGfDnos/moodlenet Trello board]. | '''''Note:''' this is a work in progress to create a high-level overview of the MoodleNet project. For more granular detail, please check out the [https://trello.com/b/wkGfDnos/moodlenet Trello board]. | ||
'' | '' | ||
=== Q1 2018 === | === Q1 2018 === | ||
Conceive | Conceive | ||
In this phase, we researched our options and came up with a high-level goal for a platform that will be of immediate use to educators. This involved talking to a lot of educators and technologists, and looking to other platforms and services for [https://docs.moodle.org/dev/MoodleNet/inspiration inspiration]. | |||
=== Q2 2018 === | === Q2 2018 === | ||
Plan | Plan | ||
This phase focused on planning how to achieve our high-level goal, deciding on the functionality it should have. We ran a [https://docs.moodle.org/dev/MoodleNet/Design_Sprint design sprint] to ensure we had a coherent plan focused on developing a Minimum Viable Product (MVP). We also hired a [https://blog.moodle.net/2018/welcome-mayel/ Technical Architect] to ensure that we make the correct [https://docs.moodle.org/dev/MoodleNet/tech technical decisions]. | |||
=== Q3 2018 === | === Q3 2018 === | ||
Develop | Develop | ||
We're currently developing prototypes and working with [https://outlandish.com Outlandish] on the [https://docs.moodle.org/dev/MoodleNet/Front-end_dev_workshop front-end development]. We've hired a [https://blog.moodle.net/2018/introducing-alex/ backend developer] who'll be building out the crucial plumbing using [https://docs.moodle.org/dev/MoodleNet/tech/stack Elixir]. | |||
=== Q4 2018 === | === Q4 2018 === | ||
Iterate | Iterate | ||
Next quarter we're iterating on existing designs and approaches, to be laser-focused on producing something of value to educators for MVP. This is the stage when the front-end and backend development work will come together. We'll also do some early testing around the sign-up procedure, to ensure there's no blockers when we come to beta testing in January 2019. | |||
=== Q1 2019 === | === Q1 2019 === | ||
Launch | Launch | ||
We're scheduled to launch the MVP of MoodleNet to a group of beta testers in January 2019. Our plan is to recruit around 100 existing Moodle users to test the platform, and rapidly iterate the platform based on their feedback. We'll then give them invites to share with friends and colleagues, meaning we grow organically and sustainably. | |||
=== Q2 2019 === | |||
Sustain | |||
We'll go into a holding pattern while we see how the platform works in practice, fix bugs, and plan future development. How users respond to the platform will inform future development, including new features and approaches to existing workflows. | |||
Revision as of 10:31, 26 September 2018
Roadmap
Note: this is a work in progress to create a high-level overview of the MoodleNet project. For more granular detail, please check out the Trello board.
Q1 2018
Conceive
In this phase, we researched our options and came up with a high-level goal for a platform that will be of immediate use to educators. This involved talking to a lot of educators and technologists, and looking to other platforms and services for inspiration.
Q2 2018
Plan
This phase focused on planning how to achieve our high-level goal, deciding on the functionality it should have. We ran a design sprint to ensure we had a coherent plan focused on developing a Minimum Viable Product (MVP). We also hired a Technical Architect to ensure that we make the correct technical decisions.
Q3 2018
Develop
We're currently developing prototypes and working with Outlandish on the front-end development. We've hired a backend developer who'll be building out the crucial plumbing using Elixir.
Q4 2018
Iterate
Next quarter we're iterating on existing designs and approaches, to be laser-focused on producing something of value to educators for MVP. This is the stage when the front-end and backend development work will come together. We'll also do some early testing around the sign-up procedure, to ensure there's no blockers when we come to beta testing in January 2019.
Q1 2019
Launch
We're scheduled to launch the MVP of MoodleNet to a group of beta testers in January 2019. Our plan is to recruit around 100 existing Moodle users to test the platform, and rapidly iterate the platform based on their feedback. We'll then give them invites to share with friends and colleagues, meaning we grow organically and sustainably.
Q2 2019
Sustain
We'll go into a holding pattern while we see how the platform works in practice, fix bugs, and plan future development. How users respond to the platform will inform future development, including new features and approaches to existing workflows.
