I've found that often number of features is a red herring in the quality of software. I wrote much more about that in Document-centric vs. Workflow-centric design, where I expounded on the differences between process-centric projects and document or object centric projects.

The central idea of my root meditation is that making your features make sense together is more important, and often far more important, than the number of identifiable independent features.

A sensible task flow is important in a generic menu-driven application centered around a document object. It's more important in designing and developing software for more specific work flows. Indeed, it's often the most important factor. It's my opinion that in many cases the process should be the central theme in the design of software, and my rationale I hope is made clear in my other node.