Standard

Continuous Delivery Practices in a Large Financial Organization. / Vassalo, Carmine; Zampetti, Fiorelli; Romano, Daniele; Beller, Moritz; Panichella, Annibale; Di Penta, Massimiliano; Zaidman, Andy.

Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016. Los Alamitos, CA : IEEE Computer Society, 2016. p. 519-528.

Research output: Scientific - peer-reviewConference contribution

Harvard

Vassalo, C, Zampetti, F, Romano, D, Beller, M, Panichella, A, Di Penta, M & Zaidman, A 2016, Continuous Delivery Practices in a Large Financial Organization. in Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016. IEEE Computer Society, Los Alamitos, CA, pp. 519-528, 32nd IEEE International Conference on Software Maintenance and Evolution (ICSME), Raleigh, United States, 2-10 October. DOI: 10.1109/ICSME.2016.72

APA

Vassalo, C., Zampetti, F., Romano, D., Beller, M., Panichella, A., Di Penta, M., & Zaidman, A. (2016). Continuous Delivery Practices in a Large Financial Organization. In Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016. (pp. 519-528). Los Alamitos, CA: IEEE Computer Society. DOI: 10.1109/ICSME.2016.72

Vancouver

Vassalo C, Zampetti F, Romano D, Beller M, Panichella A, Di Penta M et al. Continuous Delivery Practices in a Large Financial Organization. In Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016. Los Alamitos, CA: IEEE Computer Society. 2016. p. 519-528. Available from, DOI: 10.1109/ICSME.2016.72

Author

Vassalo, Carmine; Zampetti, Fiorelli; Romano, Daniele; Beller, Moritz; Panichella, Annibale; Di Penta, Massimiliano; Zaidman, Andy / Continuous Delivery Practices in a Large Financial Organization.

Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016. Los Alamitos, CA : IEEE Computer Society, 2016. p. 519-528.

Research output: Scientific - peer-reviewConference contribution

BibTeX

@inbook{048418130325493488880f6ecf3df028,
title = "Continuous Delivery Practices in a Large Financial Organization",
keywords = "Test-Driven Development, Continuous Delivery, Continuous Integration, DevOps, Agile Development, Technical Debt, Refactoring, Testing",
author = "Carmine Vassalo and Fiorelli Zampetti and Daniele Romano and Moritz Beller and Annibale Panichella and {Di Penta}, Massimiliano and Andy Zaidman",
year = "2016",
month = "10",
doi = "10.1109/ICSME.2016.72",
isbn = "978-1-5090-3807-7",
pages = "519--528",
booktitle = "Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016",
publisher = "IEEE Computer Society",
address = "United States",

}

RIS

TY - CHAP

T1 - Continuous Delivery Practices in a Large Financial Organization

AU - Vassalo,Carmine

AU - Zampetti,Fiorelli

AU - Romano,Daniele

AU - Beller,Moritz

AU - Panichella,Annibale

AU - Di Penta,Massimiliano

AU - Zaidman,Andy

PY - 2016/10

Y1 - 2016/10

N2 - Continuous Delivery is an agile software develop- ment practice in which developers frequently integrate changes into the main development line and produce releases of their software. An automated Continuous Integration infrastructure builds and tests these changes. Claimed advantages of CD include early discovery of (integration) errors, reduced cycle time, and better adoption of coding standards and guidelines. This paper reports on a study in which we surveyed 152 developers of a large financial organization (ING Netherlands), and investigated how they adopt a Continuous Integration and delivery pipeline during their development activities. In our study, we focus on topics related to managing technical debt, as well as test automation practices. The survey results shed light on the adoption of some agile methods in practice, and sometimes confirm, while in other cases, confute common wisdom and results obtained in other studies. For example, we found that refactoring tends to be performed together with other development activities, technical debt is almost always “self-admitted”, developers timely document source code, and assure the quality of their product through extensive automated testing, with a third of respondents dedicating more than 50% of their time to do testing activities.

AB - Continuous Delivery is an agile software develop- ment practice in which developers frequently integrate changes into the main development line and produce releases of their software. An automated Continuous Integration infrastructure builds and tests these changes. Claimed advantages of CD include early discovery of (integration) errors, reduced cycle time, and better adoption of coding standards and guidelines. This paper reports on a study in which we surveyed 152 developers of a large financial organization (ING Netherlands), and investigated how they adopt a Continuous Integration and delivery pipeline during their development activities. In our study, we focus on topics related to managing technical debt, as well as test automation practices. The survey results shed light on the adoption of some agile methods in practice, and sometimes confirm, while in other cases, confute common wisdom and results obtained in other studies. For example, we found that refactoring tends to be performed together with other development activities, technical debt is almost always “self-admitted”, developers timely document source code, and assure the quality of their product through extensive automated testing, with a third of respondents dedicating more than 50% of their time to do testing activities.

KW - Test-Driven Development

KW - Continuous Delivery

KW - Continuous Integration

KW - DevOps

KW - Agile Development

KW - Technical Debt

KW - Refactoring

KW - Testing

UR - http://resolver.tudelft.nl/uuid:04841813-0325-4934-8888-0f6ecf3df028

U2 - 10.1109/ICSME.2016.72

DO - 10.1109/ICSME.2016.72

M3 - Conference contribution

SN - 978-1-5090-3807-7

SP - 519

EP - 528

BT - Proceedings - 2016 IEEE International Conference on Software Maintenance and Evolution, ICSME 2016

PB - IEEE Computer Society

ER -

ID: 9159934