Chapter Continuous Anything for Distributed Research Projects

International research projects involve large, distributed teams made up from multiple institutions. These teams create research artefacts that need to work together in order to demonstrate and ship the project results. Yet, in these settings the project itself is almost never in the core interest o...

Full description

Bibliographic Details
Main Author: Griesinger, Frank (auth)
Other Authors: Domaschka, Jörg (auth), Volpert, Simon (auth)
Format: eBook
Published: InTechOpen 2018
Subjects:
Online Access:Get fulltext
LEADER 02569naaaa2200253uu 4500
001 49246
005 20210602
020 |a intechopen.72045 
024 7 |a 10.5772/intechopen.72045  |c doi 
041 0 |h English 
042 |a dc 
100 1 |a Griesinger, Frank  |e auth 
856 |z Get fulltext  |u https://library.oapen.org/handle/20.500.12657/49246 
700 1 |a Domaschka, Jörg  |e auth 
700 1 |a Volpert, Simon  |e auth 
245 1 0 |a Chapter Continuous Anything for Distributed Research Projects 
260 |b InTechOpen  |c 2018 
506 0 |a Open Access  |2 star  |f Unrestricted online access 
520 |a International research projects involve large, distributed teams made up from multiple institutions. These teams create research artefacts that need to work together in order to demonstrate and ship the project results. Yet, in these settings the project itself is almost never in the core interest of the partners in the consortium. This leads to a weak integration incentive and consequently to last minute efforts. This in turn results in Big Bang integration that imposes huge stress on the consortium and produces only non-sustainable results. In contrast, industry has been profiting from the introduction of agile development methods backed by Continuous Delivery, Continuous Integration, and Continuous Deployment. In this chapter, we identify shortcomings of this approach for research projects. We show how to overcome those in order to adopt all three methodologies regarding that scope. We also present a conceptual, as well as a tooling framework to realise the approach as Continuous Anything. As a result, integration becomes a core element of the project plan. It distributes and shares responsibility of integration work among all partners, while at the same time clearly holding individuals responsible for dedicated software components. Through a high degree of automation, it keeps the overall integration work low, but still provides immediate feedback on the quality of the software. Overall, we found this concept useful and beneficial in several EU-funded research projects, where it significantly lowered integration effort and improved quality of the software components while also enhancing collaboration as a whole. 
540 |a Creative Commons 
546 |a English 
650 7 |a Production engineering  |2 bicssc 
653 |a Continuous Delivery, Continuous Integration, Continuous Deployment, project management, software quality, DevOps, distributed software development 
773 1 0 |0 OAPEN Library ID: ONIX_20210602_10.5772/intechopen.72045_360  |7 nnaa