Boundary Objects and their Use in Agile Systems Engineering

Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders, but also makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation, but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design-science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry

Report from GI-Dagstuhl Seminar 16394: Software Performance Engineering in the DevOps World

This report documents the program and the outcomes of GI-Dagstuhl Seminar 16394 "Software Performance Engineering in the DevOps World". The seminar addressed the problem of performance-aware DevOps. Both, DevOps and performance engineering have been growing trends over the past one to two years, in no small part due to the rise in importance of identifying performance anomalies in the operations (Ops) of cloud and big data systems and feeding these back to the development (Dev). However, so far, the research community has treated software engineering, performance engineering, and cloud computing mostly as individual research areas. We aimed to identify cross-community collaboration, and to set the path for long-lasting collaborations towards performance-aware DevOps. The main goal of the seminar was to bring together young researchers (PhD students in a later stage of their PhD, as well as PostDocs or Junior Professors) in the areas of (i) software engineering, (ii) performance engineering, and (iii) cloud computing and big data to present their current research projects, to exchange experience and expertise, to discuss research challenges, and to develop ideas for future collaborations

Agile global software development communication challenges: A systematic review

Organizations have shown a significant interest in adopting human and communication-oriented agile practices for Global Software Development (GSD). Agile practices originated in the context of small and medium co-located project teams present a number of communication challenges when they are applied to the distributed GSD. There is a need to understand the underlying communication challenges of agile GSD environment. This paper adopts a Systematic Literature Review (SLR) approach and reports communication challenges in the agile GSD context. A customized literature search and selection criteria was first developed and then applied to initially identify a set of 449 papers. Finally, 22 of 449 papers, relevant to this research, were selected for this study. These final 22 papers were reviewed and 7 major categories of communication challenges were identified in the context of agile GSD. The review results of this paper are expected to help researchers and practitioners to understand communication challenges of agile GSD and develop tools, techniques and strategies to deal with these challenges. This paper is limited to the number of reviewed studies from selected databases

Distributed software development in a financial services organisation

The outsourcing of IS functionality to offshore development firms has been a growth industry that has blossomed over the last 10 years. This is as a result of organisations, seeking to optimise costs, mitigate risks, and achieve greater return on shareholder value by delegating the delivery of business information systems and applications to third party vendors. At the same time, distributed approaches to software development has arisen, there has been a growing interest in the applicability of lightweight or Agile development methodologies. As such, this paper this paper discusses experiences of a European Financial Services firm in outsourcing, and subsequently offshoring, two of its IT projects to vendor firms in India, where Agile approaches were used. The authors provide a model of the financial firm’s critical success factors presented as a frame of reference for others interested and involved in this topical area