Skip to main content

Agile software development: 15 years of the agile manifesto

Journal of Software Engineering Research and Development welcomes submissions to the thematic series on "15 Years of agile software development".

Early research on agile development focused on issues related to the adoption of agile methods [2] as well as the effectiveness of pairs in relation to individuals [9] in software development [4]. Many of those early studies focused on the investigation of team dynamics, e.g., trust, self-organization, and communication [7]; consequences of test-driven development [5]; adoption [6] and post-adoption[3] issues; as well as challenges of implementing agile in distributed settings [8].

More recently, we have seen research in agile software development and practice mature. This has been witnessed by the higher number of journal publications which emphasize empirical methods, and drawing on the theoretical discourse of more mature research fields [1].

The aim of this thematic series is to draw attention to the mature state of agile empirical research as well as to investigate new venues, in combination with other research areas that may help broaden our understanding of the myriad implications of agile software development.

Potential topics include but are not limited to:

  • Adoption of Agile / Lean
  • Agile / Lean in Distributed Environments and Large Teams
  • Agile in Government
  • Agile Practices and Future Trends, Evolution and Revolution (Technical or Managerial)
  • Agile Principles, Lean Manufacturing and Other Disciplines
  • Agile Project Management, Outsourcing and Governance in the Agile Context
  • Agile Testing & Quality: Techniques, Patterns and Automated Support
  • Conceptual Studies and Theoretical Foundations of Agile / Lean
  • Development in Distributed and Global Agile Teams
  • DevOps and Continuous Delivery
  • Experimental Studies with Agile / Lean
  • Human and Social Aspects in Agile Methods
  • Innovation and Entrepreneurship Agile
  • Lean Startups
  • Managing Technical Debt
  • Metrics, Measurements and Mining Repositories in the Context of Agile
  • Organizational Transformation and Cultural Aspects on Agile Business
  • Patterns and Anti-patterns applying Agile / Lean
  • Refactoring Issues
  • Scaling Agile to Large Corporations
  • Systems and Software Architecture and Development of Critical Systems
  • Teaching and Coaching Agile and Lean
  • Tools and Techniques on Agile / Lean
  • User Experience (UX) Environments on Agile / Lean
  • User Roles (co-participation)


Submission Instructions

Before submitting your manuscript, please ensure you have carefully read the submission guidelines for Journal of Software Engineering Research and Development. The complete manuscript should be submitted through the Journal of Software Engineering Research and Development submission system. To ensure that you submit to the correct thematic series please select the appropriate thematic series in the drop-down menu upon submission. In addition, indicate within your cover letter that you wish your manuscript to be considered as part of the thematic series on "15 Years of agile software development". All submissions will undergo rigorous peer review and accepted articles will be published within the journal as a collection.


Deadline for submissions:  20 February 2018


Guest Editors

Tiago Silva da Silva, Federal University of São Paulo (UNIFESP), Brazil

Alfredo Goldman, University of São Paulo (USP), Brazil

Frank Maurer, University of Calgary, Canada

Simone Diniz Junqueira Barbosa, PUC-Rio, Brazil


Submissions will also benefit from the usual advantages of open access publication:

  • Rapid publication: Online submission, electronic peer review and production make the process of publishing your article simple and efficient
  • High visibility and international readership in your field: Open access publication ensures high visibility and maximum exposure for your work - anyone with online access can read your article
  • No space constraints: Publishing online means unlimited space for figures, extensive data and video footage
  • Authors retain copyright, licensing the article under a Creative Commons license: articles can be freely redistributed and reused as long as the article is correctly attributed

For editorial enquiries please contact editorial@jserd.com .

Sign up for article alerts to keep updated on articles published in  Journal of Software Engineering Research and Development - including articles published in this thematic series!


References

  1. Emerging themes in agile software development. Inf. Softw. Technol. 77(C), 56–60(Sep 2016), http://dx.doi.org/10.1016/j.infsof.2016.04.018
  2. Boehm, B.: Get ready for agile methods, with care. Computer 35(1), 64–69 (Jan2002), http://dx.doi.org/10.1109/2.976920
  3. Cao, L., Mohan, K., Xu, P., Ramesh, B.: A framework for adapting agile developmentmethodologies. European Journal of Information Systems 18(4), 332–343 (2009), http://dx.doi.org/10.1057/ejis.2009.26
  4. Dingsøyr, T., Nerur, S., Balijepally, V., Moe, N.B.: A decade of agile methodologies.J. Syst. Softw. 85(6), 1213–1221 (Jun 2012), http://dx.doi.org/10.1016/j.jss.2012.02.033
  5. Janzen, D., Saiedian, H.: Test-driven development: Concepts, taxonomy, and futuredirection. Computer 38(9), 43–50 (Sep 2005), http://dx.doi.org/10.1109/MC.2005.314
  6. Mangalaraj, G., Mahapatra, R., Nerur, S.: Acceptance of software process innovations– the case of extreme programming. European Journal of Information Systems18(4), 344–354 (2009), http://dx.doi.org/10.1057/ejis.2009.23
  7. Moe, N., Dingsøyr, T., Dybå, T.: Overcoming barriers to selfmanagementin software teams. IEEE Software 26(6), 20–26 (2009),https://www.scopus.com/inward/record.uri?eid=2-s2.0-70350604164&partnerID=40&md5=7421f2781d0536b31b263c174e856d62, cited By 34
  8. Ramesh, B., Cao, L., Mohan, K., Xu, P.: Can distributed software developmentbe agile? Commun. ACM 49(10), 41–46 (Oct 2006), http://doi.acm.org/10.1145/1164394.1164418
  9. Williams, L., Cockburn, A.: Guest editors’ introduction: Agile software development:It’s about feedback and change. Computer 36(6), 39–43 (Jun 2003), http://dx.doi.org/10.1109/MC.2003.1204373