Learning more from crossing levels: Investigating agility at three levels of the organization

Scholars have tried to explain how organizations can build agile teams by only looking at one level of analysis. We argue in this short paper that lessons can be learned from organizational science results explaining variance on three different abstraction levels of organizations. We suggest agility needs to be explained from organizational (macro), the team (meso), and individual (micro) levels to provide useful and actionable guidelines to practitioners. We are currently designing such studies and hope that they will eventually result in validated measurements that can be used to prevent companies from investing in the wrong areas when trying to move towards more agility

Psychological Safety and Norm Clarity in Software Engineering Teams

In the software engineering industry today, companies primarily conduct their work in teams. To increase organizational productivity, it is thus crucial to know the factors that affect team effectiveness. Two team-related concepts that have gained prominence lately are psychological safety and team norms. Still, few studies exist that explore these in a software engineering context. Therefore, with the aim of extending the knowledge of these concepts, we examined if psychological safety and team norm clarity associate positively with software developers' self-assessed team performance and job satisfaction, two important elements of effectiveness. We collected industry survey data from practitioners (N = 217) in 38 development teams working for five different organizations. The result of multiple linear regression analyses indicates that both psychological safety and team norm clarity predict team members' self-assessed performance and job satisfaction. The findings also suggest that clarity of norms is a stronger (30\% and 71\% stronger, respectively) predictor than psychological safety. This research highlights the need to examine, in more detail, the relationship between social norms and software development. The findings of this study could serve as an empirical baseline for such, future work.Comment: Submitted to CHASE'201

Holistic analysis of the effectiveness of a software engineering teaching approach

To provide the best training in software engineering, several approaches and strategies are carried out. Some of them are more theoretical, learned through books and manuals, while others have a practical focus and often done in collaboration with companies. In this paper, we share an approach based on a balanced mix to foster the assimilation of knowledge, the approximation with what is done in software companies and student motivation. Two questionnaires were also carried out, one involving students, who had successfully completed the subject in past academic years (some had already graduated, and others are still students), and other questionnaire involving companies, in the field of software development, which employ students from our school. The analysis of the perspectives of the different stakeholders allows an overall and holistic) view, and a general understanding, of the effectiveness of the software engineering teaching approach. We analyse the results of the questionnaires and share some of the experiences and lessons learned.info:eu-repo/semantics/publishedVersio

Requirements Engineering as Creative Problem Solving: A Research Agenda for Idea Finding

This vision paper frames requirements engineering as a creative problem solving process. Its purpose is to enable requirements researchers and practitioners to recruit relevant theories, models, techniques and tools from creative problem solving to understand and support requirements processes more effectively. It uses 4 drivers to motivate the case for requirements engineering as a creative problem solving process. It then maps established requirements activities onto one of the longest-established creative problem solving processes, and uses these mappings to locate opportunities for the application of creative problem solving in requirements engineering. The second half of the paper describes selected creativity theories, techniques, software tools and training that can be adopted to improve requirements engineering research and practice. The focus is on support for problem and idea finding - two creative problem solving processes that our investigation revealed are poorly supported in requirements engineering. The paper ends with a research agenda to incorporate creative processes, techniques, training and tools in requirements projects

Creative Thinking in eXtreme Programming

Agile methods such as eXtreme Programming have achieved an explosive interest in the software development community. They can be seen as a reaction to the more traditional and control-oriented methods, agile methods handle changes in design and requirements and they open up for creativity during the whole project lifecycle. The knowledge management in agile methods is also agile, it means that knowledge creation and sharing processes are simplified in comparison with other more comprehensive development methodologies. This paper is developed under the idea that agile software development can be enhanced by a better understanding of knowledge management and creativity. eXtreme Programming is analyzed from the perspective of the creativity, we believe that concepts related to creative teams (roles, structure, performance and purposes) are important insights about the use of agile methods in general and eXtreme Programming in particular.Keywords/Index Terms: Knowledge Management; Creativity; Software Engineering; Agile Methods; User-centered innovation

From Empowerment Dynamics to Team Adaptability: Exploring and Conceptualizing the Continuous Agile Team Innovation Process

To foster their innovation teams’ adaptability, organizations are increasingly relying on agile teams. While research on the adoption of agile methods and practices has grown tremendously in the past decade, little is currently known about the human side of agile teams and how it contributes toward the emergence of adaptability. While the Agile Manifesto states that individuals and interactions are more important for agile product development than tools and processes, research on how these interactions unfold is still in its infancy. To shed light on the human side of adaptability, 44 semi‐structured, in‐depth interviews were conducted with team members and leaders from various teams at three organizations (i.e., two German and one multinational European firm). The inductive analysis identified empowerment as a focal human factor for adaptability emergence. A model of the continuous agile team innovation process is developed and uncovers the importance of dynamic empowerment states and their temporary equilibria for team adaptability. The underlying findings demonstrate that empowerment is not a static state, but rather emerges through the interactions between various actors. Specifically, the team and its leader engage in both empowerment‐enhancing and empowerment‐reducing activities. These activities are further influenced by the agile team’s immediate context: Two‐fold customer influences, that is, supporting and hindering empowerment interactions, and the organizational environment, that is, undergoing an agile transformation and supportive top management behaviors, play an important role in affecting the empowerment dynamics that result in team adaptability. As such, this study contributes to the innovation and management literatures by revealing the dynamic role of the empowerment and adaptability constructs for agile innovation processes and the importance of various actors and the organizational environment for fostering adaptability. Practical insights are offered to management, teams, and team members on how to create conditions for empowerment dynamics and consequently adaptability to unfold

Is agile project management applicable to construction?

This paper briefly summarises the evolution of Agile Project Management (APM) and differentiates it from lean and agile production and ‘leagile’ construction. The significant benefits being realized through employment of APM within the information systems industry are stated. The characteristics of APM are explored, including: philosophy, organizational attitudes and practices, planning, execution and control and learning. Finally, APM is subjectively assessed as to its potential contribution to the pre-design, design and construction phases. In conclusion, it is assessed that APM offers considerable potential for application in predesign and design but that there are significant hurdles to its adoption in the actual construction phase. Should these be overcome, APM offers benefits well beyond any individual project

Knowledge Management in Software Development

Today’s business environment is extremely dynamic and competitive. In order to sustain the pressure and gain a competitive edge, it is imperative for organizations to be creative in their software development efforts. Agile software development has huge potential for nurturing creativity. However, little research has examined creativity in the context of software development projects, particularly those using agile practices. The objective of this paper is to articulate a model that elucidates the relationship between agile practices and creativity. Further, the model tries to provide an understanding of how Knowledge Integration mediates the Relationship between agile practices and team creativity

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