MoodleNet/Roadmap: Difference between revisions
Doug Belshaw (talk | contribs) No edit summary |
Doug Belshaw (talk | contribs) No edit summary |
||
| Line 18: | Line 18: | ||
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 | 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 Mayel, our [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 | ||
In this phase we developed prototypes and worked with [https://outlandish.com Outlandish] on the [https://docs.moodle.org/dev/MoodleNet/Front-end_dev_workshop front-end development]. We hired Alex, a [https://blog.moodle.net/2018/introducing-alex/ backend developer] built out the crucial plumbing using [https://docs.moodle.org/dev/MoodleNet/tech/stack Elixir]. | |||
=== Q4 2018 === | === Q4 2018 === | ||
Iterate | Iterate | ||
This phase was about iterating existing designs and approaches so we could be laser-focused on producing something of value to educators. We onboarded Ivan as our [https://blog.moodle.net/2018/say-hello-to-ivan/ designer and front-end developer], and brought together the front-end and backend development work. We did some early testing around the [https://blog.moodle.net/2018/sign-up-feedback/ sign-up process], and re-imagined it to ensure there's no blockers for testing. | |||
----- | ----- | ||
Revision as of 15:13, 28 January 2019
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 milestones in our GitLab issue tracker.
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 Mayel, our Technical Architect to ensure that we make the correct technical decisions.
Q3 2018
Develop
In this phase we developed prototypes and worked with Outlandish on the front-end development. We hired Alex, a backend developer built out the crucial plumbing using Elixir.
Q4 2018
Iterate
This phase was about iterating existing designs and approaches so we could be laser-focused on producing something of value to educators. We onboarded Ivan as our designer and front-end developer, and brought together the front-end and backend development work. We did some early testing around the sign-up process, and re-imagined it to ensure there's no blockers for testing.
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 reflect on what went well with the MVP and ensure the platform works in practice, fixing bugs and responding to user needs. During this quarter we'll also plan and start prototyping future development, based on how users respond to the platform (including new features and analysing existing workflows).
