Use of framework synthesis to identify the factors considered for five popular prioritisation approaches

Software requirement prioritisation is an important task that ultimately determines whether the software is successful and achieves customer satisfaction. Startups use agile methodologies to develop software, as it adapts to requirement changes well and delivers software quickly in short increments, called sprints. However, there is little research about the practices of agile requirement re-prioritisation, the activity to reprioritise requirements at the start of each sprint. This research contributes to this gap by identifying the factors considered for five popular prioritisation approaches and compares them to the agile requirement re-prioritisation process. The results show that the approaches studied do not address all factors of the agile requirement re-prioritisation process. The planning game covers five of the factors whereas analytical hierarchy process covers three of the factors. This may influence the choice of approach used for agile requirement re-prioritisation. This study contributes important insights for requirement prioritisation literature and practice.