Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program

Software development projects have undergone remarkable changes with the arrival of agile development methods. While intended for small, self-managing teams, these methods are increasingly used also for large development programs. A major challenge in programs is to coordinate the work of many teams, due to high uncertainty in tasks, a high degree of interdependence between tasks and because of the large number of people involved. This revelatory case study focuses on how knowledge work is coordinated in large-scale agile development programs by providing a rich description of the coordination practices used and how these practices change over time in a four year development program with 12 development teams. The main findings highlight the role of coordination modes based on feedback, the use of a number of mechanisms far beyond what is described in practitioner advice, and finally how coordination practices change over time. The findings are important to improve the outcome of large knowledge-based development programs by tailoring coordination practices to needs and ensuring adjustment over time.Comment: To appear in Project Management Journa

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

Useful Descriptions of Organizational Processes: Collecting Data for the Process Handbook

This paper describes a data collection methodology for business process analysis. Unlike static objects, business processes are semi-repetitive sequences of events that are often widely distributed in time and space, with ambiguous boundaries. To redesign or even just describe a business process requires an approach that is sensitive to these aspects of the phenomena. The method described here is intended to generate semi-formal process representations suitable for inclusion in a "handbook" of organizational processes. Using basic techniques of ethnographic interviewing and observation, the method helps users map decomposition, specialization, and dependency relationships at an intermediate level of abstraction meaningful to participants. By connecting new process descriptions to an existing taxonomy of similar descriptions in the Handbook, this method helps build a common vocabulary for process description and analysis.

The Language of Bias: A Linguistic Approach to Understanding Intergroup Relations

[Excerpt] This chapter explores the role of language in the relationship between diversity and team performance. Specifically, we consider how a linguistic approach to social categorization may be used to study the social psychological mechanisms that underlie diversity effects. Using the results of a study examining the effects of gender, ethnicity and tenure on language abstraction, we consider the potential implications for team processes and effectiveness. In addition, we propose a revised team input-process-output model that highlights the potential effects of language on team processes. We conclude by suggesting directions for future research linking diversity, linguistic categorization and team effectiveness

Critical Factors and Multisite Implementation of ERP: A Case Study in the UAE

Despite extensive studies in the ERP literature, little empirical understanding has been reached in relation to ERP implementation experiences in developing markets, particularly in the UAE context. Derived from the notions of critical successful factors and multisite implementation, two of widely researched areas in ERP studies, this paper thus seeks to provide practical insights about organizations’ ERP implementation experiences in the UAE setting. More specifically, it describes and contrasts critical factors and multisite implementation experiences in two case organizations situated in the UAE. These case organizations, one being categorized as a global company and the other local, provide interesting comparison of ERP implementation because of their complementary organizational structure and business strategies. In contrast to traditional ERP frameworks’ suggestions, these case organizations’ experiences reveal that contemporary ERP implementations might be more complex than previously expected since none of these case organizations’ ERP experiences follows suggestions made by frameworks based. Further discussion about how to better understand and examine maturing ERP technology in an increasingly globalized business environment such as the UAE is provided

Some empirical evidence on business-IT alignment processes in the public sector: A case study report

An empirical study that explores business-IT alignment processes in a networked organization among the province Overijssel, the municipalities Zwolle and Enschede, the water board district Regge & Dinkel and Royal Grolsch N.V. in The Netherlands, is summarized in this report. The aim of the study was to identify processes that contribute to improve such alignment. This study represents a continuation of previous validation efforts that help us to confirm the business-IT alignment process areas that should ultimately be included in the ICoNOs MM. Evidence was sought for the alignment of business and IT through the use of information systems to support the requirements of the organization in a specific project. The results of this study in the public sector also are relevant to the private sector where (i) business-IT alignment plays an increasingly valuable role, and (ii) the characteristics of collaborative networked organizations are present