Table of Contents
- How Does Mendix Support Feedback Management?
- How Can Users Provide Feedback on Applications to the Development Teams?
- How Can Development Teams Communicate with Users About Submitted Feedback?
- How Can Development Teams Manage, De-Deduplicate & Prioritize Feedback?
- How Do Users Get Notifications on Planning, Progress & Resolution Status Changes?
- How Can I Integrate My Existing User Feedback Tracking System with Mendix?
Collecting feedback from users and other stakeholders, prioritizing the feedback, and acting on crucial items is essential to the success of application delivery projects, both during development and after go-live. The Mendix Platform provides development teams with the following advanced feedback management features:
- Collection of feedback from users
- Communication channels with users for submitted feedback
- Feedback management and de-duplication features
- Feedback prioritization
- Planning, progress, and resolution status notification features
This functionality enables a very fast feedback loop between the development team, stakeholders, and key end-users, in turn enabling quick improvement of the app under development. The management features enable development teams to fully integrate user feedback into their natural development cycle.
Mendix provides the Mendix Feedback Widget to empower end-users to submit feedback from the context of the app itself. Feedback items are submitted through the widget into the Feedback section of the app project in the Developer Portal. This allows end-users to easily provide valuable feedback to the app development team.
For every submitted feedback item, the Mendix Platform automatically collects the following metadata to help the development team:
- Information about the user who submitted the feedback item
- The page that was visible on the screen when the feedback item was submitted
- A screenshot of the page as it looked when the user submitted the feedback
- The application-level user role the user had
- The browser the user was using and the resolution of their screen
When a feedback item is accepted, the associated user story has the same metadata associated to it. When the story is scheduled in the current Sprint, it becomes visible in Mendix Studio Pro. From there, developers can click a link to open the page that was visible when the feedback item was submitted.
The development team can review and triage feedback items in the Feedback section of the Developer Portal. They can then communicate with the submitter of the feedback item through messages on the Buzz thread under the feedback item.
End-users can keep track of submitted feedback through the Developer Portal and post updates and replies to questions. As with all Buzz activity, email notifications are sent when someone replies to your post. Users can quickly open the Developer Portal from those emails, or just reply by email to post a response.
Once the team understands the feedback, they can decide on whether or not to accept it. This is an important step in the feedback management process, because it allows the team to immediately close feedback items (meaning, to get rid of duplicate items and close items that have been resolved) so that they do not pollute the backlog with low-priority items.
When the team decides to accept a feedback item, it becomes a user story in the backlog of their app project. The product owner can then prioritize these stories in the context of the broader product backlog. This enables the development team to focus on what is truly important and schedule these user stories as part of their Sprint planning.
In some scenarios, you might already have an existing user feedback tracking system in place that you would like to use for your Mendix apps. Through the creation and use of custom widgets, you can integrate any client-side user feedback tracking system. For server-side integrations, Mendix’s integration capabilities can be used, and in the rare case that total flexibility is required, custom Java actions can be created.