Roadmap
Our detailed roadmaps are designed to provide visibility into the development priorities for Moodle LMS and Moodle Marketplace. These roadmaps are are open and living. Click on the links below for more details about them.
What is a roadmap and why is it important?
At Moodle HQ we use roadmaps as the source of truth where we document our product direction, priorities and progress.
We use these roadmaps as the plans that align our teams, ensuring our work is focused on common goals and clear outcomes.
Who creates the roadmap and how often does it get updated?
The Moodle HQ Product teams curate every idea on the roadmap during our quarterly planning processes.
Every three months, the team takes a week off development to complete detailed planning of the work to be delivered during our next increment and map out our areas of focus for a rolling 12 to 18 months ahead.
Before each planning week, our Product leads conduct engagement sessions with our stakeholders and review a range of data sources to collect ideas and prioritise the roadmap.
Where do the ideas come from?
We curate our ideas from a wide range of sources including;
- Moodle Product teams continuously review issues created by our users who can log new feature requests and ideas for improvements in our public tracker. The issues can also be voted on by our community to mark interest in the suggestions made by others.
- Our public forums are available to all community members to obtain support and discuss ideas. They are a rich source of feedback that is used to inform our roadmap.
- Our Product Advisory Groups (PAGs), which meet on a regular basis, help inform the priorities of our roadmap ideas. These groups are formed by representatives from our user base and our Moodle Partner network with whom we work closely to define the needs of our markets in education and workplace learning.
- All members of the Moodle HQ team and our Community are encouraged to share their thoughts on the future of our open source platform and Moodle Marketplace. From new innovations to maintenance tasks, every idea is welcomed and is considered for prioritisation during our planning process.
How should the roadmaps be interpreted?
Our roadmaps are not, strictly speaking, delivery plans - we don't explicitly provide dates for each of our deliverables. The reason for this is that we know that the world around us is changing at pace, new ideas are constantly emerging and urgent issues pop up from time to time.
At Moodle HQ, we have to balance the needs of a broad range of stakeholders; the point of sharing the roadmaps is to make our prioritisation balancing act more transparent.
That's why we publish our roadmaps using the 'Now, Next, Later' methodology, detailing the current order we plan to follow in delivering new features and enhancements across our product portfolio. These phases should be interpreted as:
| Roadmap Phase | Description |
|---|---|
| 🏁 Awaiting Release | These are ideas/features that have been completed but aren't released for General Availability. It should be expected that they are in the next major release of Moodle LMS or Moodle Marketplace. |
| Now | These are ideas/features that are currently being worked on. It should be expected that these should be delivered in the upcoming release, and no more than 2 releases away. |
| Next | These ideas/features are what will be worked on once the items in "Now" are completed. They are likely currently being worked on in 'Discovery' mode only. Ideas/features in this phase would be 6-12 months away. |
| Later | These are ideas/features that we believe are important to get onto as soon as capacity allows. We want to work on them, but after the Now and Next items. |
| Later Still | These are ideas/features that we think are valid, but currently sit behind other ideas in our roadmap. We will investigate and consider them for the future. |