Abstract Tech-leading organizations are embracing the forthcoming artificial intelligence revolution. Intelligent systems replacing and cooperating with traditional software components. Thus, same development processes standards in engineering ought to be complied systems. This study aims understand by which intelligence-based developed how state-of-the-art lifecycle models fit current needs of industry. We conducted an exploratory case at ING, a global bank strong European base. interviewed...

ING Bank, a large Netherlands-based internationally operating bank, implemented fully automated continuous delivery pipe-line for its software engineering activities in more than 300 teams, that perform 2500 deployments to production each month on 750 different applications. Our objective is examine how strong metrics agile (Scrum) DevOps teams can be set an iterative fashion. We exploratory case study focuses the classification based predictive power of metrics, which we analyze log data...

What can we learn from historic data that is collected in three software companies on a daily basis had to cope with highly complex project portfolios? In this paper analyze large dataset, containing 352 finalized engineering projects, the goal discover what factors affect performance, and actions be taken increase performance when building portfolio. The projects were classified four quadrants of Cost/Duration matrix: analysis was performed strongly related two those quadrants, Good...

Tech-leading organizations are embracing the forthcoming artificial intelligence revolution. Intelligent systems replacing and cooperating with traditional software components. Thus, same development processes standards in engineering ought to be complied systems. This study aims understand by which intelligence-based developed how state-of-the-art lifecycle models fit current needs of industry. We conducted an exploratory case at ING, a global bank strong European base. interviewed 17...

Context The research literature on software development projects usually assumes that effort is a good proxy for cost. Practice, however, suggests there are circumstances in which costs and should be distinguished. Objectives: We determine similarities differences between size, effort, cost, duration, number of defects projects. Method: compare two established repositories (ISBSG EBSPM) comprising almost 700 from industry. Results: demonstrate (log)-linear relation cost the one hand,...

The appeal of delivering new features faster has led many software projects to adopt rapid releases. However, it is not well understood what the effects this practice are. This paper presents an exploratory case study releases at ING, a large banking company that develops solutions in-house, characterize Since 2011, ING shifted release model. switch resulted in mixed environment 611 teams releasing relatively fast and slow. We followed mixed-methods approach which we conducted survey with...

In this paper we explore opportunities, challenges, and obstacles that Functional Size Measurement (FSM) experts assume to be in automatically derived functional size, directly from the software project code itself. We designed a structured survey, was answered by 336 FSM specialists. A majority of respondents consider an important tool for decision making. No indications are found any perceived impact agile methodology on difficulty applying FSM. Respondents overall think automated as...

Since the rapid growth of agile development methods for software engineering, more and organizations measure size iterations, releases, projects in both function points story points. In 2011 Santana et al. performed a case study on relation between points, from data collected Brazilian Government Agency. this paper we replicate study, using Dutch banking organization. Based statistical correlation test find that comparison as measured our repository indicates moderate negative linear...

Background: During the period of one year, ING developed an approach for software analytics within environment a large number engineering teams working in Continuous Delivery as Service setting. Goal: Our objective is to examine what factors helped and hindered implementation such environment, order improve future activities. Method: We analyzed artifacts delivered by project, performed semi-structured interviews with 15 stakeholders. Results: identified 16 that analytics, 20 project....

In this paper, we attempt to understand what contributes a successful process for managing legacy system evolution. We provide an analysis of number key performance indicators such as cost, duration, and defects. By normalizing through function points, furthermore compare larger benchmark. To do so performed mixed, retrospective case study on series nine software releases eight single once-only releases, all performing single, system, in West-European telecom company. interviewed eleven...

In 2014, a Microsoft study investigated the sort of questions that data science applied to software engineering should answer. This resulted in 145 developers considered relevant for scientists answer, thus providing research agenda community. Fast forward five years, no further studies whether from engineers at hold other companies, including software-intensive companies with different primary focus (to which we refer as software-defined enterprises). Furthermore, it is not evident problems...

Context: In this paper we present an exploratory study on the insights of organizations into perceived value their software projects. Our is based notion that quantifying and qualifying project size, cost, duration defects needs to be done in relation with stakeholder satisfaction value. Objectives: We expect bringing equation will help increasing impact such deliver. Method: order find out whether our approach practically feasible industrial setting, performed a Belgian telecom company....

A medium-sized west-European telecom company experienced a worsening trend in performance, indicating that the organization did not learn from history, combination with much time and energy spent on preparation review of project proposals. In order to create more transparency supplier proposal process pilot was started Functional Size Measurement pricing (FSM-pricing). this paper we evaluate implementation FSM-pricing software engineering domain company, as an instrument useful context...

In this research we aimed to identify distinguishing factors in software releases. For purpose analyzed the metrics of 26 projects. These projects were release-based deliveries from two stable, experienced development teams. During measurement period both teams transformed a plan-driven delivery model (waterfall) an agile approach (Scrum). Overall, observed that these small differ largely non-release-based Our indicates combination working, fixed and team, steady heartbeat contribute...

Context: In this paper we describe and evaluate a tool for Evidence-Based Software Portfolio Management (EBSPM) that developed over time in close cooperation with software practitioners from The Netherlands Belgium. Objectives: goal of the EBSPM-tool is to measure, analyze, benchmark performance interconnected sets projects terms size, cost, duration, number defects, order support innovation company's delivery capability. supports building maintaining research repository finalized different...

We study whether an assumed positively skewed distribution of effort data prevents software estimators to learn over time; leading increasing differences between planned and actual a deteriorating (worsening) trend on productivity. analyze 25 releases one application, collected period six years in public sector institution The Netherlands. statistically test for distribution, versus time, productivity portfolios. key contributions this paper are that we show proposed assumption assumes any...

Based on the large amounts spent by software companies to develop new and existing systems, we argue that an evidence-based approach focuses a portfolio as whole should be in place support decision-making. We developed EBSPM evidence-based, practical model actively steer at optimization of their delivery portfolio. evaluated case studies surveys industry, demonstrate its strengths limitations practice. This lead following results: • analyzed - from point view characteristics best performers...

The development of Cloud Infra-Services has shifted over the past decade in direction a software code process, also known as infrastructure (IaC). Contemporary continuous delivery settings industry require fast feedback. As consequence, companies need insight time spent, especially such services. We examine series 28 within ING, and explore which factors affect their overall to market time. An initial perception among several stakeholders Infra-Service that ING take longer than those peer...