A HYBRID SOFTWARE DEVELOPMENT METHOD FOR LARGE-SCALE PROJECTS: RATIONAL UNIFIED PROCESS WITH SCRUM

Conventional software development methods have gradually been replaced by lightweight agile software development methods since the mid-1990s. This phenomenon is mainly due to the conventional methods’ shortcomings, including a slow adaptation to rapidly changing business requirements, and a tendency to be over budget and behind schedule. This paper analyzes characteristics, strengths, and weaknesses of both conventional and agile methods. This paper also explains the four major phases and nine disciplines of the Unified Process, and the common elements of the Scrum process. Finally, this paper suggests a new hybrid software development method that combines the Rational Unified Process with the Scrum process to accommodate the strengths of both methods while suppressing their weaknesses. The hybrid method can be utilized in the software industry, particularly, in the business sectors that deal with large-scale projects.

[1]  Ken Schwaber.  The Enterprise and Scrum , 2007 .

[2]  Peng Xu,et al.  How extreme does extreme programming have to be? Adapting XP practices to large-scale projects , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[3]  Richard T. Watson,et al.  Key Issues in Information Systems Management: An International Perspective , 1997, J. Manag. Inf. Syst..

[4]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[5]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[6]  Barry W. Boehm,et al.  Using Risk to Balance Agile and Plan-Driven Methods , 2003, Computer.

[7]  Stefan Biffl,et al.  Integrating Collaborative Processes and Quality Assurance Techniques: Experiences from Requirements Negotiation , 2004, J. Manag. Inf. Syst..

[8]  Keith W. Miller,et al.  Agile software development: human values and culture , 2005, IEEE Technology and Society Magazine.

[9]  Laurie Williams,et al.  Extreme Programming and Agile Methods — XP/Agile Universe 2002 , 2002, Lecture Notes in Computer Science.

[10]  Ken Schwaber,et al.  SCRUM Development Process , 1997 .

[11]  Allen S. Parrish,et al.  A field study of developer pairs: productivity impacts and implications , 2004, IEEE Software.

[12]  Laurie A. Williams,et al.  Agile software development: it's about feedback and change , 2003, Computer.

[13]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[14]  Noriko Hanakawa,et al.  A project management support tool using communication for agile software development , 2004, 11th Asia-Pacific Software Engineering Conference.

[15]  Gert-Jan de Vreede,et al.  Field Experiences with eXtreme Programming: Developing an Emergency Response System , 2006, J. Manag. Inf. Syst..

[16]  Scott W. Ambler,et al.  A Manager's Introduction to The Rational Unified Process (RUP) , 2005 .

[17]  Aldo Dagnino,et al.  Agile Software Development in Large Organizations , 2004, Computer.

[18]  Corrine Glesne,et al.  Becoming Qualitative Researchers: An Introduction , 1991 .

[19]  Stephen R. Schach.  Introduction to Object-Oriented Systems Analysis and Design with Uml and the Unified Process , 2003 .

[20]  Boris Gloger,et al.  Scrum , 2021, Informatik-Spektrum.

[21]  John May,et al.  Tailoring XP for Large System Mission Critical Software Development , 2002, XP/Agile Universe.

[22]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[23]  Barry W. Boehm,et al.  Understanding and Controlling Software Costs , 1988, IEEE Trans. Software Eng..

[24]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[25]  Meredith D. Gall,et al.  Educational Research: An Introduction , 1965 .

[26]  Axel Schmolitzky,et al.  Developing Complex Projects Using XP with Extensions , 2003, Computer.

[27]  Barry W. Boehm,et al.  Management challenges to implementing agile processes in traditional development organizations , 2005, IEEE Software.