Issues identified in the software process due to barriers found during eliciting requirements on agile software projects: Insights from India

Abstract

Nowadays, many of the Agile based project development teams are distributed geographically across the globe. The teams are divided into onshore and offshore that work together to achieve on a common target. The teams in turn work in small iterations to minimize the effect of change in software requirements and at the same time developing regular communication between them. However different factors such as physical distance and lack of proper communication between the onshore and offshore teams become a hurdle between them leading to misunderstandings about software requirements. Though there are many advanced way of communication like video conferencing, voice chatting is available, it certainly has several disadvantages in getting the task completed. This paper gives an insight about these challenges faced in many of the software industries and it would allow different stakeholders within agile based onshore /offshore setting to better understand these challenges in eliciting their requirements.

Challenges Faced in the Enterprise Resource Planning Material Management Section when Transitioning Towards Agile Software Development

“…This is in contrary to the negative aspects stated in other research works [11]. As all the team members are known to each other and there was only one scrum master and a Product Owner was present in the same location, there were not much of difficulties in gathering requirements as stated in the other articles [14].…”

Requirement Engineering Challenges in Agile Software Development

“…Too much implementation in initial prototyping causes issues such as quality concerns generated by the practice of reusing code in prototype, and stakeholders may not accept other development cycles which are more scalable and robust. According to Ganesh and angasamy [73], the challenges of RE lie through clear communication and information sharing, domain knowledge, and less documentation on software requirements. Primary reason is that the client and whole team are no longer available for daily face-to-face meetings.…”

eXRUP: A Hybrid Software Development Model for Small to Medium Scale Projects

“…The conventional models are presented and discussed in various papers [1][2][3][4]. In the last decade, agile models got attention of the software industry due to their unique features, such as quick response to requirement changes, reduced/pragmatic documentation and agility [5]. Authors of studies [6,7] refer to agile models as lightweight compared to conventional heavyweight models.…”