I’ve got an existing application. It’s running smoothly and I want to keep it as streamlined as possible. I’ve spent countless hours in testing and debugging. It’s not perfect but I try to make it as close. I do not want it bloated, I find convoluted UIs quite cumbersome, but business users are our main customers, they will continuously want features. They’ll ask for the moon if they could. Where do we draw the line? In my area of work being a developer and also acting as business analyst, I’ve learned to accept feature requests if they would fall under the following requisites:
1. If the request will not just be used "once off" or just for one time usage,
e.g. "create a feature that can generate me the end of year financial statement for 2009"
2. If the request is requested by more than one person in more than one different team. It doesn’t mean that if a stakeholder keeps asking for the same feature over a period of time that it’s a good idea.
3. Feature request is useful to everyone that uses the system, not just useful to a handful of people. Maximize ROI.
4. Does not slow down or complicate any existing feature.