<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Call for Papers: Special issue on "Towards a unified view of agile software development"<br>Journal of Systems and Software<br><br>Almost ten years have elapsed since the articulation of the agile<br>manifesto. The intervening period has witnessed significant changes in<br>the practice of software development. A number of agile practices and<br>methods, such as pair programming, test-driven development, feature<br>driven development, kanban, planning poker, coding dojos, kaizen,<br>extreme programming, Scrum, Crystal Clear and lean development, are in<br>use in companies. Despite the tremendous strides that we have made,<br>there is yet no clear understanding of the efficacy of such<br>practices. The current situation is reminiscent of the early days of<br>object-orientation (OO) when practitioners had to choose from a<br>perplexing array of methods and practices, with no apparent consensus<br>in the field to guide their actions. As we approach the tenth<br>anniversary of the agile manifesto (February, 2011), it would be<br>worthwhile for scholars and practitioners to examine the myriad<br>changes that have occurred in software development.<br><br>In particular, it is important for us to address several questions,<br>including the following: Has the proliferation of methods, practices,<br>tools and techniques taken us away from the ideals originally<br>articulated in the manifesto? Has there been a change/evolution in the<br>principles and ideals in the manifesto? Can we discern an underlying<br>unified theme across these methods and practices? Does the evolution<br>of ideas share patterns of similarity with epistemological advances in<br>other relevant fields?<br><br>For this special issue, we would like to invite contributions that<br>critically reflect on the current status of research and practice in<br>agile development. In particular, we would like contributions<br>questioning and exploring the theoretical underpinnings of agile and<br>lean development and the agile manifesto. Theoretical articles must<br>include some empirical evaluation or substantive discussion of<br>implications for practice.<br><br>Submissions:<br>Articles can either be submitted directly to the special issue, or be<br>selected for the special issue from papers submitted to the Agile2011<br>conference (<a href="http://www.agile2011.org/">www.agile2011.org</a> see separate call for papers). For<br>direct submission, articles must be formatted according to Journal of<br>Systems and Software guidelines:<br>(<a href="http://www.elsevier.com/wps/find/journaldescription.cws_home/505732/">http://www.elsevier.com/wps/find/journaldescription.cws_home/505732/</a><br>authorinstructions#16001).<br><br>Manuscripts must be submitted via the online submission and peer<br>review systems at <a href="http://ees.elsevier.com/jss">http://ees.elsevier.com/jss</a>. Follow the submission<br>instructions given on this site. Please select the article type as<br>“Special Issue: Agile Development”.<br><br>Key dates:<br>* Agile 2011 submission deadline: 25 February 2011<br>* Direct special issue submission starts: 1 July 2011 (the article<br>type “Special Issue: Agile Development” will open for submission)<br>* Direct special issue submission deadline: 1 August 2011<br>* Acceptance/rejection notification: 15 November 2011<br>* Revised manuscripts ready: 1 January 2012<br><br>Guest Editors:<br>* Torgeir Dingsøyr, SINTEF, Norway<br>* Nils Brede Moe, SINTEF, Norway<br>* Sridhar P Nerur, University of Texas at Arlington, USA<br>* VenuGopal Balijepally, Prairie View A&M University, USA<br>
<br></body></html>