Here is the scenerio.
You have 20 feature requests and you have 100 people.
You want to work on the top 2 feature requests for the next version from all 100 people or possibly top 4 if you have the resources based on the requirements.
50 people click they want 20 features 10 people click they don't want 10 of the features.
You now have 20 features that are the "top".
Ex. your output would be
feature 1 (50 want it)
feature 2 (50 want it)
all the way down to feature 20
Now if you had 50 people rate 1-5 on 20 features and you had 10 people rate a 0 on the features you would be able to take the top rated features since they would start averaging out.
Ex. your output would be
feature 1 (4.5 stars)
feature 2 (3.2 stars)
so on
Yes they could vote 5 stars for all the features but in time they will realize 2 or 4 are picked for each version and they need to prioritize their "top".
A real cool way but probably harder is everyone gets 10 points to put on the bugs/features for the next version. They can put up to 5 per bug/feature. They can also replace the points if they change their mind.
It would work kind of like a draft system and at any point in time you could get the top 2 features based on popularity.
Right now the only way that seems to solve it is having a feature/bug issue in project point to a thread that can be thread voted so you can sort by top feature/bug post. Just a little confusing for the end user and will probably require some intervention to line up.
|