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.
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.
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.
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.
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.
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).