Factors Affecting Cloud Infra-Service Development Lead Times: A Case Study at ING
H.K.M. Huijgens (ING Bank)
Eric Greuter (ING Bank)
Jerry Brons (ING Bank)
Evert A. van Doorn (ING Bank)
Ioannis Papadopoulos (ING Bank)
Francisco Morales Martinez (Student TU Delft)
Maurício Aniche (TU Delft - Software Engineering)
O.W. Visser (TU Delft - Computer Science & Engineering-Teaching Team)
A. van Deursen (TU Delft - Software Technology)
More Info
expand_more
Other than for strictly personal use, it is not permitted to download, forward or distribute the text or part of it, without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license such as Creative Commons.
Abstract
The development of Cloud Infra-Services has shifted over the past decade in the direction of a software code development process, also known as infrastructure as code (IaC). Contemporary continuous delivery settings in industry require fast feedback. As a consequence, companies need insight in time spent, especially in the development of such services. We examine a series of 28 Cloud Infra-Services within ING, and explore which factors affect their overall time to market and development time. An initial perception among several stakeholders in the Cloud Infra-Service development process, that Cloud Infra-Services within ING take longer than those in peer companies, is not confirmed by our benchmark. Development team members identified the time to internal market of services to be affected negatively by the portal where consumers can order a service and the Orchestration Workflows and by team dynamics. This perception is supported by additional metrics. We propose that promising ways to reduce lead time include reducing the complexity of the ING environment, by treating Cloud Infra-Services like regular software deliveries and by reducing the dependencies between teams in terms of tooling and collaboration.