|
| Authors | Type of project/source | Reported challenges |
|
| Dikert et al. [80] | Different cases of companies using different agile models in projects, i.e., banking, telecommunication, and distributed system | Missing high-level requirement management, refinement challenges, gap between short- and long-term planning, hard to create and estimate user stories |
| Mishra and Mishra [79] | Complex software development projects such as supply chain management having unstable and uncertain requirement | Long duration of RE due to complex decision making process, difficulty in creating and maintaining requirement priority list |
| Bjarnason et al. [81] | A case study of CASE company which develops embedded systems | The reported challenges using agile practices for large-scale software projects are planning, weak requirement in start, weak requirement prioritization and effort estimation, quality issues, customer proxy role, taking innovation, ensuring RE, validation and verification, motivation for requirement work, lack of requirement documentation |
| Rolland et al. [82] | SCRUM model-based large-scale project signed by GOV in order to modernize their existing legacy system | Scale product owners so that they manage to facilitate the requisite “translation” of user stories, which are usually multiple, including complex interdependencies, and relatively high-level development teams |
| Xu [83] | Discuss coordination challenges faced in large-scale agile projects | The reported challenges are lack of coordination in terms of decision making, communication, and control mode |
|
