Sumé LMS public roadmap

🌠 View the official Sumé LMS public product roadmap

Our product roadmap is where you can learn about what features we're working on, what stage they're in, and when we expect to bring them to you.

The roadmap repository is for communicating Sumé LMS’ roadmap. Existing issues are currently read-only, and we are locking conversations, as we get started.

Have any questions or comments about items on the roadmap? Share your feedback via public discussions.

Guide to the roadmap

Every item on the roadmap is an issue, with a label that indicates each of the following:

• A release phase that describes the next expected phase of the roadmap item. See below for a guide to release phases.

• A feature area that indicates the area of the product to which the item belongs. For a list of current product areas, see below.

• A feature targets that indicates the main user target of the product to which the item belongs. For a list of current product targets, see below.

• Once a feature is delivered, the shipped label will be applied to the roadmap issue and the issue will be closed with a comment linking to the relevant Changelog.

Release phases

Release phases indicate the stages that the product or feature goes through, from early testing to general availability.

• alpha: Primarily for testing and feedback.
  Limited availability, requires pre-release agreement. Features still under heavy development, and subject to change. Not for production use, and no documentation, SLAs or support provided.

• beta: Publicly available in full or limited capacity.
  Features mostly complete and documented. Timeline and requirements for GA usually published. No SLAs or support provided.

• ga: Generally available to all customers.
  Ready for production use with associated SLA and technical support obligations. Approximately 1-2 quarters from Beta.

Some of our features may still be in the exploratory stages, and have no timeframe available. These are included in the roadmap only for early feedback. These are marked as follows:

• in design: Feature in discovery phase.
  We have decided to build this feature, but are still figuring out how.

• exploring: Feature under consideration.
  We are considering building this feature, and gathering feedback on it.

Roadmap stages

The roadmap is arranged on a project board to give a sense for how far out each item is on the horizon. Every product or feature is added to a particular project board column according to the quarter in which it is expected to ship next. Be sure to read the disclaimer below since the roadmap is subject to change, especially further out on the timeline. You'll also find an Exploratory column, which is used in conjunction with the in design and exploring release phase labels for when no timeframe is yet available.

Feature areas

The following is a list of our current product areas:

• a11y: Acessibility features
• activity: Course Activity features
• behaviour advisor: Behaviour Advisor features
• course: Course features
• data: Data platform integration features
• forum: Forum features
• guardian: Guardian features
• learning path: Learning path features
• message: Message features
• security: General security features
• other: Other features

Feature targets

The following is a list of our current feature targets:

• educator: The target user is the Educator
• student: The target user is the Student
• administrator: The target user is the System Administrator

Create an initiative

The following is the list of steps for Sumé LMS Product Managers to follow in order to create new feature issues:

1. Create a issue
2. Use the following template:

### Summary

Can you summarize the feature or business requirement that justify this initiative?

### Intended Outcome

What is the desired outcome for this? What are the expected results? What define the success?

### How will it work?

Can you explain or describe one or more scenarios for this? How it should work? Who is going to interact with this?

Do not forget to use a descritive, but short title to the issue.

3. Add the relative labels to it.

Disclaimer

Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to team as of the date they are made, and Sumé Solutions assumes no obligation to update any forward-looking statements. The forward-looking product roadmap does not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and is intended to outline the general development plans. Customers should not rely on this roadmap to make any purchasing decision.

---

This was based on Github's public roadmap