3. Effected number of users / or frequency of use
This factor is product specific, not everywhere considered as prioritization factor. The functionality may be prioritize by keeping in mind the number of users will be effected. for an example, in a eCommerce web site look and feel of consumer home page will get higher priority than a supplier home page.
Similarly if a functionality will be used more often, that should be prioritize early to work on any additional optimization work for it if needed.
4. Cost to develop and implement the functionality
High cost not necessarily be on low priority, we need to think rationally, about each functionality’s cost and ROI. Cost is not the only factor, during prioritizing we need to think about the return of the functionality as well.
Definitely Low cost – High return will be on top priority and similarly High cost – low return can be low priority. But High cost – high return can also be at top of the list, considering other factors of prioritization.
5. Risks
Ranking high risks functionality in top of the list, maximize the early mitigation. Where keeping high risk functionality for later stage of the project, increase overall risk of implementation.
6. Complexity
Functionality with high complexity or difficult, is advisable to start working on early stages of the project, As the team is fresh so allocation of skilled and experience member is easy. And If it takes more time than estimated, the team will also have more room to adjust the extra time.