Table 4 Literature work of papers presenting new reprioritization technique and case studies
From: Exploring reprioritization through systematic literature surveys and case studies
S. no. | Paper reference | Findings and deliverable | Future work/limitations |
|---|---|---|---|
1. | Gupta et al. (2014b) | Decision aspects reprioritization is not undertaken by organizations, but they do recognize the need for handling requirements. Staying in markets by reducing the development efforts (especially time and cost) is one of the criteria that make them reluctant for reprioritizing already prioritized requirements. This aims to get insight into prioritization and reprioritization of both decision aspects and requirements. Updated documentation is another finding of the case study | The area of reprioritization is explored to finer levels by interactions with organizations that had been using agile and non agile models from the time since back. The interactions should only focus around reprioritization Although the presented case study had been done with mass market software development organizations and had flavoured the tastes of both agile as well as non agile software developments |
2. | Gupta et al. (2013) | Technique for performing reprioritization of new, changed and delayed requirements | Not evaluated on real case studies May not be suitable for reprioritization of pairwise comparison based requirements beyond some value of a number of requirements |
3. | Gupta et al. (2014a) | Technique to perform reprioritization of pairwise compared requirements with minimal efforts It has good coverage of requirement set and involves minimal pairwise comparisons | Should be extended to reprioritize decision aspects Should be executed on evolutionary software with thousands of requirements and continuous flood of requirements |
4. | Kukreja and Boehm (2013) | This paper provides a two step process model for performing prioritization and reprioritization. Reprioritization is facilitated by automatic re-computation of requirement priorities by changing the priorities of parent MMF as per changing business environment | Techniques not evaluated on real mass market situations like ever increasing requirements, aspects and stakeholders |