Agile Large-Scale Software Development: Success Factors, Challenges and Solutions

Amro Mohammad Hani Al-Said Ahmad*
Department of Computer Science, Amman, Jordan.
Periodicity:January - March'2014
DOI : https://doi.org/10.26634/jse.8.3.2807

Abstract

Many challenges and obstacles have been arising when Agile methods are being used in large-scale projects. But as software engineers, we always try to find ways to overcome the problems and challenges. As Agile has been presented as a very good method that deals with change (that considers a big and serious challenge in traditional SE methodologies) it must not be ignored by project managers and team leaders in large-scale projects. This study presents a number of recommendations and solution that highlights on using modern communications technologies and social media websites in the process of maintaining the element of permanent connection between the team members, and it helps sharing the domain knowledge between team members to deal with social skills, Agile training, documentation, decision making, and testing. The study has been divided into three main subjects: first is how to gain success in largescale projects and how to gain success attributes upon using Agile method, the second is the challenges faced upon using Agile in the global distributed environment project, the third is to suggest a recommendation to overcome each challenge that certainly will help the project manager to deal if any challenge occurs.

Keywords

Agile adoption, Large-Scale Success Factor, Agile Large-Scale Software Development, Agile Challenges

How to Cite this Article?

Ahmad,A.M,H,A. (2014). Agile Large-Scale Software Development: Success Factors, Challenges and Solutions. i-manager’s Journal on Software Engineering, 8(3), 1-12. https://doi.org/10.26634/jse.8.3.2807

References

[1]. Arora A. (2008). Agile Automation Testing, Adobe Systems, India Pvt. Ltd, Noida.
[2]. Boehm B., Turner R. (2005). Management Challenges to Implementing Agile Processes in Traditional Development Organizations, IEEE Software, Sep-Oct, 30- 39.
[3]. Cao L. and Ramesh B. (2008). Agile Requirements Engineering Practices: an Empirical Study, IEEE Software, January/February, 60-67.
[4]. Conboy K., Coyle S. and Others (2011). People over process: key people challenges in Agile Development, IEEE Software, July-Aug, 48-57.
[5]. Drury M., Conboy K. and Power K. (2012). Obstacles to decision making in Agile software development, The Journal of Systems and Software, 85(6), 1239-1254.
[6]. Herbsleb D. & Mockus A. (2003). An empirical study of speed and communication in globally distributed software development, IEEE Transactions on Software Engineering, 29(6), 481-494.
[7]. Holmstrom H., Fitzgerald B., and Others (2006). Agile Practices Reduce Distance in Global Software Development, Information Systems Management, Summer, 7- 26.
[8]. Hossain E., Babar M, and Paik H. (2009). Risk Identification and Mitigation for Using Scrum in Global Software Development: A Conceptual Framework, 16th Asia-Pacific Software Engineering Conference.
[9]. Jureczko M. (2008). The Level of Agility in Testing Process in a Large Scale Financial Software Project. Software Engineering Techniques in Progress, University of Technology, Poland.
[10]. Kan S. (2003). Metrics and Models in Software Quality Engineering, 2nd edition, Addison-Wesley, Boston, MA.
[11]. Koteska B, and Mishev A. (2012). Agile Software Testing Technologies in a Large Scale Project, BCI Local, Volume 920 of CEUR Workshop Proceedings, 121-124.
[12]. Moe N., Aurum A. & Dybå T (2012). Challenges of Shared Decision-Making: A Multiple Case Study of Agile Software Development, Journal of Information and Software Technology, 54 (8), 853–865.
[13]. Nerur, S. and Mahapatra R. (2005). Challenges of Migrating to Agile Methodologies, Communications of the ACM, 48(5), 73-78.
[14]. Paulish D. (2002). Architecture-Centric Software Project Management, Addison-Wesley, Boston, MA.
[15]. Pressman R. (2010). Software Engineering: A Practitioner's Approach, 7th edition, The McGraw-Hill Companies, Inc, USA.
[16]. Rajlich V. (2012). Software Engineering: The Current Practice, Taylor and Francis Group, USA.
[17]. Sangwan R., Bass M., Mullick N., Paulish D., and Kazmeier J (2007). Global Software Development Handbook, Taylor & Francis Group, LLC, USA.
[18]. Shrivastava S. and Date H. (2010). Distributed Agile Software Development: A Review, Journal of Computer Science and Engineering, 1(1), 10-17.
[19]. Tenhunen T. (2010). Challenges in Scaling Agile Sof tware Development, Tampere University of Technology, Master Thesis.
[20]. Williams, R., Pandelios, G., and Behrens, S. (1999). SRE Method Description (version 2.0) & SRE Team Members Notebook (Version 2.0), Technical Report CMU/SEI-99-TR-029, Carnegie Mellon University.
[21]. Ylimannela, V. (2010). A Model for Risk Management in Agile Software Development, [Accessed: 13 Sep, 2013] http://www.cloudsw.org/underreview/ 1af0cbb6-6d4c-4082-8530-17e1317e2ceb/ a6f468c9-4857-4206-96ee-f67df0583d41.
If you have access to this article please login to view the article or kindly login to purchase the article

Purchase Instant Access

Single Article

North Americas,UK,
Middle East,Europe
India Rest of world
USD EUR INR USD-ROW
Pdf 35 35 200 20
Online 35 35 200 15
Pdf & Online 35 35 400 25

Options for accessing this content:
  • If you would like institutional access to this content, please recommend the title to your librarian.
    Library Recommendation Form
  • If you already have i-manager's user account: Login above and proceed to purchase the article.
  • New Users: Please register, then proceed to purchase the article.