Advice on Managing SW Enhancement Requests - Links

From https://www.novell.com/communities/coolsolutions/what-happens-enhancement-requests/:

Once I have seen the request I generally do one of 4 things with it almost immediately.
1. If I know that this is a duplicate of another request I close the new one and mark it as a duplicate of the original.
2. If I see no value to the request, or I see value but the opportunity cost is too high, then I will just close it.
3. If I see value to the request, and it fits in with much of the feedback received on all of the other channels then I will assign it to be considered for a release
4. Finally I can choose to do nothing with it right now. This final one allows me to bear it in mind and use it for consideration on future requests.

From http://support.aha.io/hc/en-us/articles/202000757-Best-practices-to-managing-and-prioritizing-features:

1. You need to know what the goals or key business drivers are for your product so you can create a scorecard that includes these key metrics.;
2. If it is not clear who owns prioritization, your scoring will not be trusted. It's essential to know who is in charge;
3. If there is not enough detail per feature, then the functionality of each feature will be unclear.

From http://johnpeltier.com/blog/2013/12/12/feature-requests/:

1.  Ideas that don’t fit with the long term vision for the product at all.  These receive a polite rejection.
2. Many, many good ideas that you might do someday.  These are usually acknowledged but sit in the “someday” bucket.
3. A few ideas which map to the area of the product that needs work next, or the next most important problem to solve.

Once prioritized, you’ll want to communicate your plans in a roadmap that doesn’t tie you to specific dates.

From https://www.quora.com/How-should-a-product-manager-handle-communication-to-internal-people-who-make-feature-requests-when-the-volume-of-requests-far-exceeds-engineering-capacity:

The backlog should not be a dumping ground for all ideas that may get worked on eventually, or may not. It will become impossible to manage and just gives the requestor a false sense of security by having it added. If you don't see yourself working on a backlog item in the next ~4 months, I recommend just telling the person no, point blank, or maintaining a separate list or roadmap outside of the backlog for these items.