Abstract

AbstractThis paper shows the necessary steps, which should be taken in order to get the most out of agile software development in interdisciplinary settings involving scientific experts. If applied properly, Agile delivers increased productivity, higher quality and, last but not least, higher customer satisfaction. The task of developing high quality software is already difficult. Developing software for a new IT-enabled service in an interdisciplinary team however, is even more challenging.In interdisciplinary projects scientific experts from different fields need to work together with computer scientists, developers, testers, business analysts and domain experts. Software engineering is very time-consuming and scientific experts who have never been involved in a software project, often find it hard to understand why progress sometimes seems so slow. Therefore, it is important that they understand what it takes to write high-quality code, i.e. code that is clean, tested, documented and extendable at the right points. The best way to achieve this goal is to expand the software team, make the scientific experts an integral part of it and thus profit from their know-how.

Highlights

  • In the last decade, there has been a shift away from traditional towards agile software methodologies

  • There are several reasons that brought about this shift from traditional, Big Design Up Front1 (BDUF) to Agile Software Development [7], [10]

  • The sixth annual “State of Agile Development” survey [11] sheds some light on the benefits of Agile Software Development and its worldwide adaption

Read more

Summary

Introduction

There has been a shift away from traditional towards agile software methodologies. Many people felt that the overhead imposed by traditional methods like the waterfall model, Unified Process etc. Slowed down the development process and did not deliver the needed quality. Many companies and software developers have adopted agile methodologies like Scrum [1], eXtreme Programming [2] (XP), Lean [4] or Kanban [5]. There are several reasons that brought about this shift from traditional, Big Design Up Front (BDUF) to Agile Software Development [7], [10]. The sixth annual “State of Agile Development” survey [11] sheds some light on the benefits of Agile Software Development and its worldwide adaption. The survey data includes information from more than 6,000 respondents from different countries and was collected at the end of 2011

Objectives
Methods
Findings
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call