Built to Last or Built Too Fast? Evaluating Prediction Models for Build Times

Automated builds are integral to the Continuous Integration (CI) software development practice. In CI, developers are encouraged to integrate early and often. However, long build times can be an issue when integrations are frequent. This research focuses on finding a balance between integrating often and keeping developers productive. We propose and analyze models that can predict the build time of a job. Such models can help developers to better manage their time and tasks. Also, project managers can explore different factors to determine the best setup for a build job that will keep the build wait time to an acceptable level. Software organizations transitioning to CI practices can use the predictive models to anticipate build times before CI is implemented. The research community can modify our predictive models to further understand the factors and relationships affecting build times.Comment: 4 paged version published in the Proceedings of the IEEE/ACM 14th International Conference on Mining Software Repositories (MSR) Pages 487-490. MSR 201

Agile development for a multi-disciplinary bicycle stability test bench

Agile software development methods are used extensively in the software industry. This paper describes an argument to explain why these methods can be used within a multi-disciplinary project and provides a concrete description on how to implement such a method, using a case-study to support the rationale. The SOFIE (Intelligent Assisted Bicycle) project was created to develop mechatronic appliances to make bicycles more stable, i.e. safer. A bicycle stability test bench is created within this project and is used as the case study for this research. The relative complexity of the test bench development and partner structure within the SOFIE project has many similarities with large-scale complex projects found in industry. Thus it provides a good environment to research the application of Agile software methods to a multi-disciplinary project

Safety-Critical Systems and Agile Development: A Mapping Study

In the last decades, agile methods had a huge impact on how software is developed. In many cases, this has led to significant benefits, such as quality and speed of software deliveries to customers. However, safety-critical systems have widely been dismissed from benefiting from agile methods. Products that include safety critical aspects are therefore faced with a situation in which the development of safety-critical parts can significantly limit the potential speed-up through agile methods, for the full product, but also in the non-safety critical parts. For such products, the ability to develop safety-critical software in an agile way will generate a competitive advantage. In order to enable future research in this important area, we present in this paper a mapping of the current state of practice based on {a mixed method approach}. Starting from a workshop with experts from six large Swedish product development companies we develop a lens for our analysis. We then present a systematic mapping study on safety-critical systems and agile development through this lens in order to map potential benefits, challenges, and solution candidates for guiding future research.Comment: Accepted at Euromicro Conf. on Software Engineering and Advanced Applications 2018, Prague, Czech Republi

Towards a New Framework for Product Development

In the mid-1980s, Andreasen and Hein first described their model of Integrated Product Development. Many Danish companies quickly embraced the principles of integrated product development and adapted the model to their specific business and product context. However, there is concern amongst many Danish companies that Integrated Product Development no longer provides a sufficient way of describing industry’s product development activity. More specifically, five of these companies have supported a programme of research activities at the Technical University of Denmark, which seeks to develop a new framework for product development. This paper will describe the research approach being taken, present some initial findings, and outline a vision of a new working approach to product development

Challenges of open innovation: the paradox of firm investment in open-source software

Open innovation is a powerful framework encompassing the generation, capture, and employment of intellectual property at the firm level. We identify three fundamental challenges for firms in applying the concept of open innovation: finding creative ways to exploit internal innovation, incorporating external innovation into internal development, and motivating outsiders to supply an ongoing stream of external innovations. This latter challenge involves a paradox, why would firms spend money on R&D efforts if the results of these efforts are available to rival firms? To explore these challenges, we examine the activity of firms in opensource software to support their innovation strategies. Firms involved in open-source software often make investments that will be shared with real and potential rivals. We identify four strategies firms employ – pooled R&D/product development, spinouts, selling complements and attracting donated complements – and discuss how they address the three key challenges of open innovation. We conclude with suggestions for how similar strategies may apply in other industries and offer some possible avenues for future research on open innovation

Unleashing the Effectiveness of Process-oriented Information Systems: Problem Analysis, Critical Success Factors, Implications

Process-oriented information systems (IS) aim at the computerized support of business processes. So far, contemporary IS have often fail to meet this goal. To better understand this drawback, to systematically identify its rationales, and to derive critical success factors for business process support, we conducted three empirical studies: an exploratory case study in the automotive domain, an online survey among 79 IT professionals, and another online survey among 70 business process management (BPM) experts. This paper summarizes the findings of these studies, puts them in relation with each other, and uses them to show that "process-orientation" is scarce and "process-awareness" is needed in IS engineering

CRM excellence at KLM Royal Dutch Airlines.

This case article tells the story of the rebirth of CRM at KLM Royal Dutch Airlines since 2002 and its successful liftoff during 2003, for which KLM received Gartner’s 2004 CRM Excellence Award. The Award presents itself as a natural moment of reflection on past CRM achievements and future plans. The case works well for generating a multifaceted class discussion on the challenge of making CRM into a business success. More specifically, it allows us to (1) dissect a CRM success story, that contrasts nicely with many of the CRM horror stories of the 1990s, and identify key success factors; (2) focus attention onto the viability of the planned approach KLM uses for implementing CRM; (3) introduce and show the importance of program management as a construct for structurally growing and governing enterprise wide investment in CRM; and (4) help reinforce lessons around CRM and business-ICT alignment.

The Real World Software Process

The industry-wide demand for rapid development in concert with greater process maturity has seen many software development firms adopt tightly structured iterative processes. While a number of commercial vendors offer suitable process infrastructure and tool support, the cost of licensing, configuration and staff training may be prohibitive for the small and medium size enterprises (SMEs) which dominate the Asia-Pacific software industry. This work addresses these problems through the introduction of the Real World Software Process (RWSP), a freely available, Web-based iterative scheme designed specifically for small teams and organisations. RWSP provides a detailed process description, high quality document templates - including code review and inspection guidelines - and the integrated tutorial support necessary for successful usage by inexperienced developers and teams. In particular it is intended that the process be readily usable by software houses which at present do not follow a formal process, and that the free RWSP process infrastructure should be a vehicle for improving industry standards