“…Through an industrial case study, Peterson and Wohlin 20 found that the main advantages of implementing agile and incremental practices in large‐scale software development can be listed as follows: (1) requirements are more precise due to reduced scope and thus easier to estimate, (2) direct communication in teams reduces the need for documentation, (3) early feedback due to frequent deliveries, (4) rework reduction, (5) testing resources are used more efficiently, (6) higher transparency of who is responsible for what creates incentives to deliver higher quality, (7) low requirements volatility in projects and (8) reduction of waste (discarded requirements) in the requirements engineering process. Agile practices such as evolutionary requirements, pair‐programming and direct stakeholder involvement have been proven to be successful for the development of large‐scale systems 21, 22. Few studies reported that some practices from agile methodologies such as iterative development, frequent testing and feedback, small release and refactoring are suitable for large projects, while others like stand‐meetings and the use of metaphors are not appropriate 17, 19.…”