A product team always works under constraints of resources, time and quality; while there are always abundance of requirements which need to be implemented. We have also seen that a product need not have too many functions, since most of the customers use only about 10-20 % of the functionality, as indicated by many empirical studies. Many products (like iPod SchuffleShuffle) are a living testimony of this theory. In this article, we will look at the "Requirements Prioritization" process.
...