After having seen requirements definition (with User Stories) and modelling (with CRC cards), we deal now with Software Requirements Prioritization, that is how to decide which requirements should be scheduled. We see both examples from heavy-weight methods (AHP, SQF), and agile requirements (Planning Poker and Planning Game).

• Software Requirements Prioritization

Some additional material:

• describing how AHP can be applied: Saaty, Thomas L. "Decision making with the analytic hierarchy process." International journal of services sciences 1.1 (2008): 83-98.
• the importance of eigenvalues in AHP: Saaty, Thomas L. "Decision-making with the AHP: Why is the principal eigenvector necessary." European journal of operational research 145.1 (2003): 85-91.
• the application of QFD (interesting pages to look at as an example are pages 50-65): Kivinen, Terhi. "Applying QFD to improve the requirements and project management in small-scale project." University of Tampere, Department of Computing Sciences, Computer sciences (2008).