Route Improvement Requests

We receive 5-10 improvement requests from our customers every day. Some of them are good, and some are not very good. I can easily choose the ones with which I agree, but I would like to organize the rest well, so if we get a lot of similar requests, we can determine priorities accordingly.

We have a big lag behind good ideas, so the request will usually not be added to the work queue unless we see strong demand from customers. This makes it impractical, so it makes no sense to track them with our current work item tracking (TFS). The main goal of their organization is so that we can see where demand is strongest, and we can determine which features are most important to our users.

Any suggestions are welcome.

+3
source share
2 answers

I saw small applications that allow people to add queries, and anyone can vote for them. This will show you what people are most interested in using this particular system, although depending on the implementation, it can be very susceptible to games. Take a look at something like UserVoice . They probably do most of the work for you.

+2
source

Source: https://habr.com/ru/post/1723233/


All Articles