(Shrivastava & Date, 2010, p. 10) observed on various topics which are beneficial for the software development projects when the distributed teams are using agile methodologies. Sprint reviews could be an efficient method to enhance exterior communiqué while they assist to share data about the needs and feature dependencies amongst stakeholders. (Nilsson & Karlsson, 2014) also reiterated that agile practices such as sprint review and retrospectives are also team ceremonies, which, if performed properly, could address some of the challenges in communication. In the sprint review the project team will have an opportunity to gather feedback from the customer and other stakeholders on a regular basis and at short intervals. Customer requests for changes in requirements and priorities for the next iteration can also be communicated to the team.
(Shrivastava & Date, 2010, p. 10) also studied the impact on trust and confirms that use of agile frameworks can also help in generating trust between people of different cultures involved in the process by regular communication and delivery of software.
(Paasivaara & Lassenius, 2006, p. 4) further analyzed the impact on customers, business when using agile in distributed teams and stated that from customer’s point of view this way of software development and implementation provides extra flexibility when the customer is able to ask for changes during the development phase without having a lot of time-consuming discussions with subcontractors. Further, the customer establishment gets empowered to introduce subcontractors into the assignment already in the initial stages of growth, when the customer is not yet able to define the requirements in a detailed manner but can only rely on early correction of direction when needed.