New in Mendix 3.0: 7 Steps to Better Feedback, Faster

Skip Navigation

New in Mendix 3.0: 7 Steps to Better Feedback, Faster

/ August 3, 2011

Mendix 3.0 has plenty of new features worth discussing, particularly its built-in feedback mechanism. Many of the new features are meant to keep applications up to speed with constantly changing business demands; that’s how Mendix facilitates agile application lifecycle management. One of the key elements of business agility and meeting complex business demands is the ability to respond to change. That’s where our new feedback mechanism comes in: collaboration between business and IT. Let’s break it down into 7 steps:

Step 1: Connect sprintr to your app.

Connect sprintr to your app example

When you start building a new app in Mendix, make sure to enable Team Server so that your development team can collaborate with business end-users easily. Keeping business users involved throughout the project may seem overwhelming, but don’t worry – sprintr will keep their input organized and prioritized.

Step 2: Download the feedback widget.

Download the feedback widget screenshot

Download the feedback widget from the Mendix AppStore and configure it within your Business Modeler. It will give your app this intuitive feedback button on every page.

Step 3: Gather feedback from stakeholders.

Business Supplies Feedback

Feedback to be accepted or Rejected

Users of your application, including those on the development team, can click the feedback button to provide their input. These feedback tickets will have all the meta data you’ll need to properly assess business (or development) needs.

Step 4: Organize feedback into your backlog.

feedback appears in sprintr

Feedback tickets can be accepted and added to your backlog, rejected to ask for more information, or ignored if its a known issue.

Step 5: Feedback easily becomes new user story.

Feedback gets accepted

Feedback is put into sprintr as a User Story

Feedback tickets that uncover new requirements for the project can be made new tasks or user stories in the appropriate upcoming sprintr. This is how the feedback mechanism continues to evolve your application – if you didn’t gather this feedback now, it might turn into a real headache later on.

Step 6: View user stories from within the Business Modeler.

User Story Appears in Modeler

Now when you’re modeling the application in the Business Modeler, your new feedback inspired user story will be shown underneath your development environment. You can even double click the user story to jump directly to the form it’s associated with.

Step 7: Respond to change orders.

Commit changes

To keep the feedback issuer informed on your progress with their input; let them know by changing the feedback ticket from ‘Running’ to ‘Done’. They’ll only get an email if they checked off the ‘please keep me updated’ box when submitting feedback – they’ll be happy to see the progress.

Copy link