One of the biggest problems/concerns seen in any project is scope creep. So it is important during the requirement gathering stage itself that we limit the scope creep. This can be done by prioritizing requirements. Prioritizing requirements is very useful especially when there are too many functions and features to implement compared to the time and budget provided
So prioritization of requirements should be done based on the following factors:
- Stakeholder priorities -> Each of the major stakeholder has a different list of priorities. It is important to prioritize these requirements if you want the project to be given the green signal
- Value to business and end user -> The requirements which provide the highest return on investment to the business and end user must be prioritized
- Cost and Time -> Requirments which require the least time and cost to develop should be prioritized
Now after each of the requirements must be listed and each of the above factors must be scored on a scale of 1 to 5. The requirements with the highest totals should be prioritized for implementation.