Login Register Cart 0
Generic placeholder image

Recent Patents on Engineering

Editor-in-Chief

ISSN (Print): 1872-2121
ISSN (Online): 2212-4047

Back
Journal Home About Journal Editorial Board Journal Insight Current Issue Volumes/Issues
Subscribe
Review Article

Agile Approach as a Universal Remedy for the Usual Failure in the Development of Software Projects

Author(s): Sonam Srivastava* and Ashwani Kumar

Volume 15, Issue 2, 2021

Published on: 17 January, 2020

Page: [188 - 194] Pages: 7

DOI: 10.2174/1872212114666200117112617

Price: $65

Abstract

Background: Agile is not a methodology neither can it be considered as a peculiar way of developing any software also it is neither a framework nor a process. Agile is a mindset or a collection of beliefs that can be used by the teams for taking the decisions while working on any software development. Agile mindset adopted for the development of software has gained attention of the researchers and industries across the world because otherwise the software project would turn out to be uncertain and very turbid. The universal remedy for the usual failure of the software project development is the agility. Actually saying agile is nothing novice instead it is a meta model based on best practices from the preceding models like waterfall, iterative, incremental and rapid application development method.

Objective: The objective of this paper is to highlight various points of comparison between them and conclude that failing fast is failing cheap in case of agile for software development.

Methods: So, we can say that an agile always existed but not in a structured and a formal manner. The two main methodologies of agile as an umbrella term are XP and scrum.

Results: Thus in this paper we have discussed about scrum as a major methodology and also how various scrum roles contribute towards making teams self-organized to reduce the usual rate of failure of development projects.

Conclusion: The success rate of the software applications developed through the agile concept is three times than that of the traditional waterfall method and also the percentage of cost and time overruns is much lower.

Keywords: Agile approach, software development, extreme programming, scrum, scrum master, proxy product owner.

Graphical Abstract

[1]
O. Salo, and P. Abrahamsson, "Agile methods in European embedded development organizations: A survey study of extreme programming and scrum", IET Softw., vol. 2, pp. 58-64, 2008.
[http://dx.doi.org/10.1049/iet-sen:20070038]
[2]
M. Brhel, H. Meth, A. Maedche, and C. Werder, "Exploring principles of user-centered agile software development: A literature review", Inf. Softw. Technol., vol. 61, pp. 163-181, 2015.
[http://dx.doi.org/10.1016/j.infsof.2015.01.004]
[3]
K. Gama, "Preliminary findings on software engineering practices in civic hackathons", IEEE/ACM CSI-SE, pp. 14-20, 2017.
[http://dx.doi.org/10.1109/CSI-SE.2017.5]
[4]
H. Alahyari, R.B. Svensson, and T. Gorschek, "A study of value in agile software development organizations", J. Syst. Softw., vol. 125, pp. 271-288, 2017.
[http://dx.doi.org/10.1016/j.jss.2016.12.007]
[5]
M. Unterkalmsteiner, T. Gorschek, A. Islam, C.K. Cheng, R. Permadi, and R. Feldt, "Evaluation and measurement of software process improvement: A systematic literature review", IEEE Trans. Softw. Eng., vol. 38, pp. 398-424, 2012.
[http://dx.doi.org/10.1109/TSE.2011.26]
[6]
M. Paasivaara, and C. Lassenius, Scaling scrum in a large globally distributed organization: A Case StudyIEEE ICGSE, pp. 74-83-83, 2016.
[http://dx.doi.org/10.1109/ICGSE.2016.34]
[7]
C. Scharff, "Guiding global software development projects using scrum and agile with quality assurance", IEEE CSEE T, pp. 274-283, 2011.
[http://dx.doi.org/10.1109/CSEET.2011.5876097]
[8]
P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta, “Agile software development methods: Review and analysis”, VTT Technical Research Centre of Finland, VTT Publications 478., Otamedia, 2002.
[9]
S. Stavru, "A critical examination of recent industrial surveys on agile method usage", J. Syst. Softw., vol. 94, pp. 87-97, 2014.
[http://dx.doi.org/10.1016/j.jss.2014.03.041]
[10]
P. Abrahamsson, J. Warsta, and M.T. Siponen, "New directions on agile methods: A comparative analysis", J. Syst. Softw., vol. 81, pp. 961-971, 2003.
[http://dx.doi.org/10.1109/ICSE.2003.1201204]
[11]
T. Chow, and D. Cao, "A survey study of critical success factors in agile software projects", J. Syst. Softw., vol. 81, pp. 961-971, 2008.
[http://dx.doi.org/10.1016/j.jss.2007.08.020]
[12]
N. Baruah, Int. J. Comput. Appl., vol. 47, pp. 38-44, 2012.
[13]
J. Highsmith, Computer, vol. 34, pp. 120-127, 2012.
[http://dx.doi.org/10.1109/2.947100]
[14]
K. Kuusinen, "Overcoming challenges in agile user experience work: Cross-case analysis of two large software organizations", IEEE SEAA, pp. 454-458, 2015.
[http://dx.doi.org/10.1109/SEAA.2015.38]
[15]
R. Hoda, J. Noble, and S. Marshall, "Self-organizing roles on agile software development teams", IEEE Trans. Softw. Eng., vol. 39, pp. 422-444, 2013.
[http://dx.doi.org/10.1109/TSE.2012.30]
[16]
T. Hanusiak, M. Klak, K.K. Skibski, and T. Zaras, "Agile software development process and results", U.S. Patent US20160098270A1.
[17]
R. Holler, I. Culling, R. Delwadia, P. Mamut, M. Crowe, D. Hanson, P. Boudreaux, D. Gilkerson, J. Brooks, E. Farr, and J. Odenwelder, "Transitioning between iterations in agile software development", U.S. Patent US8561012B1.
[18]
S. Dorairaj, J. Noble, and G. Allan, "Agile software development with distributed teams: senior management support", In: IEEE ICGSE, 2013.
[http://dx.doi.org/10.1109/ICGSE.2013.33]
[19]
A. Marchenko, and P. Abrahamsson, "Scrum in a multiproject environment: an ethnographically inspired case study on the adoption challenges", Agile 2008 Conf, 2008pp. 15-26
[http://dx.doi.org/10.1109/Agile.2008.77]
[20]
J.M. Bass, "Scrum master activities: process tailoring in large enterprise projects", IEEE ICGSE, pp. 6-15, 2014.
[http://dx.doi.org/10.1109/ICGSE.2014.24]
[21]
R.M. Fontana, I.M. Fontana, P. Garbuio, S. Reinehr, and A. Malucelli, "Processes versus people: How should agile software development maturity be defined?", J. Syst. Softw., vol. 97, pp. 140-155, 2014.
[http://dx.doi.org/10.1016/j.jss.2014.07.030]
[22]
A. Kumar, S.P. Ghrera, and V. Tyagi, "Implementation of wavelet based modified buyer-seller watermarking protocol", WSEAS Trans. Sig. Pro, vol. 10, pp. 212-220, 2014.
[23]
A. Kumar, "Design of Secure Image Fusion Technique Using Cloud for Privacy-Preserving and Copyright Protection", IJCAC, vol. 9, pp. 22-36, 2019.
[http://dx.doi.org/10.4018/IJCAC.2019070102]
[24]
A. Kumar, S.P. Ghrera, and V. Tyagi, "An ID-based Secure and Flexible Buyer-seller Watermarking Protocol for Copyright Protection", Pertanika J. Sci. Technol., vol. 25, pp. 57-76, 2017.
[25]
R. Holler, I. Culling, R. Delwadia, P. Mamut, M. Crowe, D. Hanson, and P. Boudreaux, "Integrated planning environment for agile software development", U.S. Patent US9690461B2.
[26]
C. Vankar, The adoption of agile software development methodologies by organisation in South Africa., University Of Kwazulu-Natal: South Africa, 2015.
[27]
K.J. Smiley, C.L. Louis, V. Augustine, S. Sharma, I. Nistor, A. Cordes, and O. Becker, "Overcoming the challenges of agile for globally distributed industrial research", Insight, vol. 21, pp. 34-38, 2018.
[http://dx.doi.org/10.1002/inst.12202]

Rights & Permissions Print Cite
Article Metrics
13
1
© 2024 Bentham Science Publishers | Privacy Policy