The Importance of Conflict Resolution Techniques in Autonomous Agile Teams

Today, software companies usually organize their work in teams. Social science research on team development has shown that for a team to reach a productive and autonomous stage, it has to be able to manage internal conflicts and disagreements efficiently. To better facilitate the team development process, we argue that software engineers' needs additional training in negotiation skills and conflict resolution. In this position paper, we outline ideas for what aspects to consider in such training. As an example, we argue that a majority of the conflicts originate from team-level factors and that they, therefore, should be managed on the team-level instead of in relation to dyads.Comment: Accepted at 1st International Workshop on Autonomous Teams (A-TEAMS), 201

Autonomous agile teams: Challenges and future directions for research

According to the principles articulated in the agile manifesto, motivated and empowered software developers relying on technical excellence and simple designs, create business value by delivering working software to users at regular short intervals. These principles have spawned many practices. At the core of these practices is the idea of autonomous, self-managing, or self-organizing teams whose members work at a pace that sustains their creativity and productivity. This article summarizes the main challenges faced when implementing autonomous teams and the topics and research questions that future research should address

Misaligned Values in Software Engineering Organizations

The values of software organizations are crucial for achieving high performance; in particular, agile development approaches emphasize their importance. Researchers have thus far often assumed that a specific set of values, compatible with the development methodologies, must be adopted homogeneously throughout the company. It is not clear, however, to what extent such assumptions are accurate. Preliminary findings have highlighted the misalignment of values between groups as a source of problems when engineers discuss their challenges. Therefore, in this study, we examine how discrepancies in values between groups affect software companies' performance. To meet our objectives, we chose a mixed method research design. First, we collected qualitative data by interviewing fourteen (\textit{N} = 14) employees working in four different organizations and processed it using thematic analysis. We then surveyed seven organizations (\textit{N} = 184). Our analysis indicated that value misalignment between groups is related to organizational performance. The aligned companies were more effective, more satisfied, had higher trust, and fewer conflicts. Our efforts provide encouraging findings in a critical software engineering research area. They can help to explain why some companies are more efficient than others and, thus, point the way to interventions to address organizational challenges.Comment: accepted for publication in Journal of Software: Evolution and Proces

Understanding Work Practices of Autonomous Agile Teams: A Social-psychological Review

The purpose of this paper is to suggest additional aspects of social psychology that could help when making sense of autonomous agile teams. To make use of well-tested theories in social psychology and instead see how they replicated and differ in the autonomous agile team context would avoid reinventing the wheel. This was done, as an initial step, through looking at some very common agile practices and relate them to existing findings in social-psychological research. The two theories found that I argue could be more applied to the software engineering context are social identity theory and group socialization theory. The results show that literature provides social-psychological reasons for the popularity of some agile practices, but that scientific studies are needed to gather empirical evidence on these under-researched topics. Understanding deeper psychological theories could provide a better understanding of the psychological processes when building autonomous agile team, which could then lead to better predictability and intervention in relation to human factors

Experimenting with Realism in Software Engineering Team Projects: An Experience Report

Over Several years, we observed that our students were sceptical of Software Engineering practices, because we did not convey the experience and demands of production quality software development. Assessment focused on features delivered, rather than imposing responsibility for longer term `technical debt'. Academics acting as 'uncertain' customers were rejected as malevolent and implausible. Student teams composed of novices lacked the benefits of leadership provided by more experienced engineers. To address these shortcomings, real customers were introduced, exposing students to real requirements uncertainty. Flipped classroom teaching was adopted, giving teams one day each week to work on their project in a redesigned laboratory. Software process and quality were emphasised in the course assessment, imposing technical debt. Finally, we introduced a leadership course for senior students, who acted as mentors to the project team students. This paper reports on the experience of these changes, from the perspective of different stakeholders

From supply chains to demand networks. Agents in retailing: the electrical bazaar

A paradigm shift is taking place in logistics. The focus is changing from operational effectiveness to adaptation. Supply Chains will develop into networks that will adapt to consumer demand in almost real time. Time to market, capacity of adaptation and enrichment of customer experience seem to be the key elements of this new paradigm. In this environment emerging technologies like RFID (Radio Frequency ID), Intelligent Products and the Internet, are triggering a reconsideration of methods, procedures and goals. We present a Multiagent System framework specialized in retail that addresses these changes with the use of rational agents and takes advantages of the new market opportunities. Like in an old bazaar, agents able to learn, cooperate, take advantage of gossip and distinguish between collaborators and competitors, have the ability to adapt, learn and react to a changing environment better than any other structure. Keywords: Supply Chains, Distributed Artificial Intelligence, Multiagent System.Postprint (published version

Human Psychology Factors Influencing Agile Team Autonomy in Post-Pandemic Remote Software Organizations

Agile project management methods are gaining in popularity in the software industry as software development teams are being asked to be adaptive to market needs and resilient to change and uncertainty. With increasing market uncertainty, global competition, and time-to-market pressure, it is becoming a challenge to develop an innovative product and deliver it on-time without the opportunity that comes from team autonomy to experiment and learn from failures in a remote workplace. To resolve this challenge, it is critical to understand the myriad human psychological factors in play that influence Agile team autonomy in a remote work environment. The role of human psychological factors on Agile project delivery success has been largely neglected or superficially covered in extant literature. The purpose of this research study was to study the influence of key human psychological factors on emergence of Agile team autonomy that leads to Agile project success in software organizations. The findings will help Information Systems researchers and practitioners in proactively identifying and addressing human psychology factors challenges to achieve successful delivery of innovative products using Agile Scrum methodology. Using an online survey instrument, the study sampled 137 software professionals from US software companies with experience in the Agile Scrum role of Team Member. The quantitative data generated was analyzed using multiple linear regression. The relationship between the independent variables – the human psychology factors pertaining to Leadership Style, Organization Structure, HR Practices and Stakeholder Engagement and the dependent variable - Agile team autonomy is explained through multiple linear regression. As multiple items are linked to variables, the statistical analysis was performed using the median scores for each variable. One-way ANOVA and Pearson’s correlation coefficient were used to demonstrate the existence (or nonexistence) of relationships between variables. Finally, an empirical model relating the human psychology factor variables and the dependent variable of Agile team autonomy was constructed for the population

Self-Organizing is not Self-Managing: A Case Study about Governance Challenges in an Agile IT Unit and its Scrum Projects

This paper presents a case study on the internal governance of Scrum projects and their relationships with their organization’s governance within a rich research setting: an IT agile unit and its mature Scrum project teams. This study reveals ambiguities about the meaning of self-organizing versus self-managing, and the associated challenges for governance processes, especially those related to HR governance, which can lead to unresolved issues and conflicts. Interestingly, these ambiguities are also found in the current IS literature, which rarely differentiates self-organizing from self-managing in agile projects. Thus, this paper enhances our knowledge of governance processes and associated challenges, particularly for mature Scrum project teams, which are still little covered in the IS literature

ELECTRONIC REQUIREMENTS NEGOTIATION – A LITERATURE SURVEY ON THE STATE-OF-THE-ART (23)

In the software development process, requirements negotiation is an essential part in which stakeholders jointly have to come to an agreement. Such a negotiation process is often conducted using information systems, which makes it an electronic requirements negotiation process. The aim of the current paper is to present the state-of-the-art in electronic requirements negotiations. We elicit the state-of-the-art by analysing relevant literature, extracting areas of current research, and describing the status quo of each area. The identified areas of research are foundations of electronic requirements negotiation, electronic requirements negotiation methodology, automation of electronic requirements negotiation, computer- mediated communication, and social communication