Skip to main content
All CollectionsProduct Updates
How to share feature requests
How to share feature requests

This article describes how the roadmap process of Grasple designed and how you can contribute to it by sharing feature requests.

Sofie Bastiaansen avatar
Written by Sofie Bastiaansen
Updated over a week ago

Grasple is a SaaS application, which means that we are continuously updating our platform and seeking improvements. We work with development cycles of six weeks, in which our technical team takes on feature improvements to ensure security, stability and didactive development on our platform.

One way in which we map possible improvements, is by collaborating closely with the actual users of Grasple, users like you! We therefore want to ensure that you can articulate your needs and wishes to our team. The process of how to go about this varies based on the size of the group that works with our platform at your institution. Below you will find which route is applicable to you!

  • NOTE: bugs can always directly be reported to our support team (via chat or email)

Institutions with a process in place

If you're a teacher / lecturer at an organisation with a Functional Application Manager for Grasple, you can submit your ideas with them. They will make sure to share your ideas with us.

If you are not sure whether your organisation has a Functional Application Manager, please send a message to us via chat or email. We will let you know whether this is the case and who to contact.

Individual users

If your institution does not have a general contact in place to communicate with us about feature requests, you can fill out a form via the button below. We will get back to you if there are any further questions or to update you on the status of the request.

Thank you for your input!

Our way of working

For some context, here is how our development process works:

  • We work in structured development ‘cycles’ that are six to eight weeks long.
    A cycle will often consist of one or two big projects and always a number of smaller tasks. Since big software projects are hard to plan, we work by the principle of ‘fixed time, flexible scope’. During the cycle, we will deliver the most important parts and see how far we get with the lower priority tasks.

  • We determine our priorities by looking at the collective input from our users. We look for synergies between multiple requests to make sure our new features serve as many users as possible. In addition, we always prioritise the projects that are necessary to keep as Grasple secure and stable as you've come to expect.

  • We roll out new features continuously, and keep an overview of updates here.

  • This approach enables you to influence our roadmap and to see what we're working on. At the same time, this process enables us to work on our development projects with the essential focus that is required to create high-quality and stable software.

  • NOTE: Because of the volume of incoming requests, we cannot promise to implement them all. We do promise to take your requests into serious consideration in our product development plans.

  • If you have any questions about this process, please let us know by contacting!

Did this answer your question?