Empirical Evaluation of the Proposed eXScrum Model: Results of a Case Study

Agile models promote fast development. XP and Scrum are the most widely used agile models. This paper investigates the phases of XP and Scrum models in order to identify their potentials and drawbacks. XP model has certain drawbacks, such as not suitable for maintenance projects and poor performance for medium and large-scale development projects. Scrum model has certain limitations, such as lacked in engineering practices. Since, both XP and Scrum models contain good features and strengths but still there are improvement possibilities in these models. Majority of the software development companies are reluctant to switch from traditional methodologies to agile methodologies for development of industrial projects. A fine integration, of software management of the Scrum model and engineering practices of XP model, is very much required to accumulate the strengths and remove the limitations of both models. This is achieved by proposing an eXScrum model. The proposed model is validated by conducting a controlled case study. The results of case study show that the proposed integrated eXScrum model enriches the potentials of both XP and Scrum models and eliminates their drawbacks.

[1]  Sara Jones,et al.  Agile Requirements Can We Have Our Cake and Eat It Too? , 2010, IEEE Software.

[2]  Tony Clear,et al.  Documentation and agile methods: striking a balance , 2003, SGCS.

[3]  Ethan Hadar,et al.  Agile architecture methodology: long term strategy interleaved with short term tactics , 2008, OOPSLA Companion.

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

[5]  Steven Fraser,et al.  Architecture in an agile world , 2009, OOPSLA Companion.

[6]  Sean Stolberg,et al.  Enabling Agile Testing through Continuous Integration , 2009, 2009 Agile Conference.

[7]  Philippe Kruchten,et al.  Software architecture and agile software development: a clash of two cultures? , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[8]  Ken Orr,et al.  Agile requirements: opportunity or oxymoron? , 2004, IEEE Software.

[9]  Lucas Layman,et al.  Toward a framework for evaluating extreme programming , 2004, ICSE 2004.

[10]  Manish Kumar,et al.  Towards knowledge assisted agile requirements evolution , 2010, RSSE '10.

[11]  Bran Selic,et al.  Agile Documentation, Anyone? , 2009, IEEE Software.

[12]  Steven Fraser,et al.  Architecture in an agile world , 2009, OOPSLA Companion.

[13]  Tom J. Bang An Agile Approach to Requirement Specification , 2007, XP.

[14]  Joaquim Baptista,et al.  Agile documentation with uScrum , 2008, SIGDOC '08.

[15]  Orit Hazzan,et al.  Agile software testing in a large-scale project , 2006, IEEE Software.

[16]  Armin Eberlein,et al.  A Framework for Requirements Engineering PRocess DEvelopment (FRERE) , 2008, 19th Australian Conference on Software Engineering (aswec 2008).

[17]  James Madison,et al.  Agile Architecture Interactions , 2010, IEEE Software.

[18]  Jeff Sutherland,et al.  Distributed Scrum: Agile Project Management with Outsourced Development Teams , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[19]  Thomas Sauer Using design rationales for agile documentation , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[20]  Daniel Sundmark,et al.  What Does Research Say about Agile and Architecture? , 2010, 2010 Fifth International Conference on Software Engineering Advances.

[21]  Shahryar Sarkani,et al.  Communication and Quality in Distributed Agile Development: An Empirical Case Study , 2010 .

[22]  Li Jiang,et al.  A Framework for Requirements Engineering PRocess DEvelopment (FRERE) , 2008 .

[23]  Yongxiang Hu The Application and Research of Software Testing on Agile Software Development , 2010, 2010 International Conference on E-Business and E-Government.

[24]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[25]  Paul A. Beavers,et al.  Managing a Large "Agile" Software Engineering Organization , 2007, Agile 2007 (AGILE 2007).

[26]  Scott W. Ambler,et al.  Lessons in Agility From Internet-Based Development , 2002, IEEE Softw..