Request-implementation ratio as an indicator for requirements prioritisation imbalance

Abstract

Software development organizations strive to implement features that will bring the highest business value to existing and prospective clients; hence the importance of requirements elicited directly from clients. However, some requirements need to be put into the backlog due to time and resource constraints in the development organization. Consequently, there have been numerous prioritisation approaches published in the literature and used in practice.