Agile Scrum Issues at Large-Scale Distributed Projects: Scrum Project Development At Large

2. Agile Model

The agile model is now very popular and vast in use SDLC (software development life cycle model). First, the term agile was used in the 1990’s for the first time in many publish papers by different researchers and practitioners. In these papers, a new idea was discussed that people (researchers and practitioners) looking for new creative, efficient and attractive approach to develop the software application in a good manner. The Jim Smith and Bob Martin were involved in the agile concept and arranged a workshop in this regard. In the workshop, they arranged ideas about the agile with others who also involved in the agile concept. In the results of that workshop, the complete agile manifesto came up in 2001. Now the agile model is very trendy in use in many software industries. The agile model design to response the particular challenges of the software industry such as no physical deliverable, short development cycle etc. An agile model is an evolutionary approach that produces high-quality software products in a cost-effective and within time (Balaji & Murugaiyan, 2012; Vijayasarathy & Turk, 2008; Moe et al., 2010; Butt, 2016). The popularity of the agile model between different software industries rather than other life cycle model is due to its unique features such it works with the small team members with 3-9 members to develop a particular software application. It gives many progressive results when using for small-scale projects in small organizations. The most owing feature of the agile model is to allow change request at any stage of the project and at any sprint/iteration. The study shows that usual times scale spends on the planning of sprints in agile software development. The agile model works in sprints as shown below in Figure 1. The agile model provides the rapid, simple and incremental/iterative development to break down the project in smaller steps. The agile model split the project in small sprints and develops iteratively. It allows the customer to direct participation in the project development and requirement elicitation. In the agile model, the customer prioritizes the requirements. The customer can send a change request at any time and at any level of the project. The agile model gives first priority to client satisfaction. The agile model replaces the traditional software development project values such as responding to change over following a plan (Dingsøyr & Moe, 2014; Sekitoleko & Evbota, 2014; Moe et al., 2010; Doyle & Williams, 2014; Butt & Jamal, 2017).