So, -how many features to include? The fact that seems to be ignored is that more features are better, -if they’re useful, and included usefully. There is a reason to lampoon companies like Microsoft, and Adobe, -they deserve it. They add items to bullet-point lists with no regard for product integrity, or actual performance.

So when is a feature useful, when is it a pain? The simple answer is “when it gets in the way, -it’s un-useful.” The problem with evolutionary development is that features tend to get stuck in odd spaces. Features that are planned for, find accurate and useful homes. Features that get incorporated in late phases tend to be incorporated in the place of least resistance.

The challenge of developers is to “say no” -or to “say yes” but not take the easy route. If incorporation of a useful feature requires modifications to 10 other screens, -then so be it.