Search results

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

This paper aims to close the gap between the generic concept of knowledge activities (KAs) and implementing them in the context of software engineering organisations concentrating on the non-technical aspects, such as team organisation and practices.

This qualitative research used a questionnaire with practitioners such as software developers and team leads who were asked to provide feedback on a set of team practices and measures typically used in software engineering projects and assess their relation to the activities of acquiring, codifying, storing, maintaining, transferring and creating knowledge. The obtained results were analysed using frequency analysis and further descriptive statistics yielding a matrix linking the investigated team practices and measures to KAs.

Team practices and measures commonly applied in software engineering can be facilitated to trigger particular KAs. While most of these team practices and measures originate from agile methods, they are not restricted to these. A purposeful composition can help in assembling a balanced set of KAs aimed at fostering given knowledge goals in software engineering organisations.

By bridging the communication and terminology gap between knowledge management research and software engineering practitioners, this work lays the foundation for assessing software teams’ knowledge profiles more easily and creating prerequisites for implementing knowledge management by facilitating common practices and measures often already part of their daily work. Hence, overhead can be avoided when implementing knowledge management.

To the best of the authors’ knowledge, this is the first study investigating application and relevance of KAs in the software industry by linking them to practices and measures well-accepted in software engineering, thus providing the necessary vocabulary for the implementation of knowledge management in software development teams.

This study aims to investigate the effects of organizational culture factors on the selection of software process development models and develops a conceptual model for selecting and adopting process development models with an organizational culture approach, using 12 criteria and their sub-criteria defined in Fey and Denison’s model (12 criteria).

The research hypotheses were investigated using statistical analysis, and then the criteria and sub-criteria were selected based on Fey and Denison’s model and the experts’ viewpoints. Afterward, the organizational culture of the selected company was measured using the data from 2016 and 2017, based on Fey and Denison’s questionnaire. Due to the correlation between the criteria, using the decision-making trial and evaluation technique, the correlation between sub-criteria were determined, and by analytical network process method and using Super-Decision software, the process development model was preferred to the 12 common models in information systems development.

Results indicated a significant and positive effect of organizational culture factors (except the core values factor) on the selection of development models. Also, by changing the value of organizational culture, the selected process development model changed either. Sensitivity analysis performed on the sub-criteria implied that by changing and improving some sub-criteria, the organization will be ready and willing to use the agile or risk-based models such as spiral and win-win models. Concerning units where the mentioned indicators were at moderate and low limits, models such as waterfall, V-shaped and incremental worked more appropriately.

While many studies were performed in comparing development models and investigating their strengths and weaknesses, and the impact of organizational culture on the success of information technology projects, literature indicated that the impact of organizational sub-culture prevailing in the selection of development process models has not been investigated. In this study, new factors and indicators were addressed affecting the selection of development models with a focus on organizational culture. Correlation among the factors and indicators was also investigated and, finally, a conceptual model was proposed for proper adoption of the models and methodologies of system development.

This study seeks to illuminate the managerial tensions inherent in implementing scaled agile (on the organizational, top management, middle management and team levels) and to frame these challenges within the broader context of project management.

The study adopts a grounded theory approach and delves into a qualitative dataset sourced from 34 interviews with subject matter experts actively engaged in scaling agile initiatives within large organizations spanning various industries. Additionally, the data have been enriched through a comprehensive literature review of the existing body of knowledge on scaling agile.

As a result of our investigation, we propose a framework of managerial tensions in scaling agile in large corporate settings and a series of research propositions and questions that may contribute significantly to the body of knowledge surrounding the phenomenon of “deprojectification” and propose agenda for the future studies in the field of project management.

The study also carries significant managerial implications. Firstly, based on the insights from the practice of scaling agile in large corporate setting, management can build awareness of the challenges inherent of transitioning to agile practices. This may help to anticipate the possible problems and proactively develop strategies how to address them. Secondly, management can be instructed about contingencies inherent in scaling agile, along with the potential disfunctions and side effects (unintended outcomes) that may emerge during the transition process. Thirdly, project management practitioners can gain insights on how scaling agile may cause shifts in the approach to managing projects, project team management and competencies that need to be developed to cope with environments where various approaches to managing projects coexist.

These insights can aid in the agile transition process, beginning with directing managerial attention toward contextual factors and progressing through potential challenges at the organizational, top management, middle management and team levels. Furthermore, the study highlights possible dysfunctionalities and side effects of scaling agile, shedding light on the “dark side” of agile.

The study contributes to the expansion of the empirical database on the implementation of agile practices in large organizational settings. It plays a role in defining and delineating the phenomenon of scaling agile within the context of project management and outlines a research agenda for future project management studies. Additionally, our study adds to the ongoing discourse surrounding the “deprojectification” effect that can occur during the scaling of agile. Lastly, it establishes connections between project management and software development literature regarding the implementation of agile at scale.

Drawing on goal-setting theory and team effectiveness theory, the study aims to examine the impact of agile taskwork and agile teamwork on team performance. In addition, it investigates the mediating effect of project commitment on the impact of agile taskwork and agile teamwork on team performance. Furthermore, the study also tests the moderating role of career level on the impact of agile taskwork and agile teamwork on team performance.

Survey data were collected from 563 employees working in 290 information technology (IT) companies in India using a self-reporting structured questionnaire. Partial least squares path modeling was used to test the hypothesized model, and the Process macro was used to test the moderating effect.

The results show that agile taskwork and agile teamwork positively affect team performance and project commitment, and project commitment positively impacts team performance. Furthermore, project commitment fully mediates the relationship between agile taskwork and team performance and partially mediates the relationship between agile teamwork and team performance. Furthermore, the career level negatively moderates the impact of agile taskwork and agile teamwork on team performance.

The study shows the importance of agile work practices and project commitment to enhance team performance. Thus, the study provides managers with two strategies to improve their team performance.

There is a scarcity of research examining the distinct effects of agile taskwork and agile teamwork on team performance and the mediating role of project commitment in these relationships. Furthermore, as per the empirical evidence, no previous research has empirically examined the moderating role of career level in the agile taskwork-team performance and agile teamwork-team performance relationships.

Literature reveals ongoing debates around the role of business analysts in agile software development (ASD) teams. This can be attributed, in part, to a knowledge gap concerning how business analysts contribute to overall team capabilities, particularly those which are essential in enabling teams to respond to fast-paced environmental changes. The purpose of this study was to address this gap by investigating how business analysts (BAs) contribute to the dynamic capabilities of ASD teams.

Through a deductive approach, this study adapted and applied a research model based on the team dynamic capabilities (DC) theory to explore the contributions of BAs in agile teams. The study was executed using a qualitative, single case study research strategy directed at an ASD team in the financial services industry. Moreover, data were collected through face-to-face, semi-structured interviews; a focus group; non-participant observation and physical artefacts review. The thematic analysis technique was used to analyse the data.

The study contributes to teams DC theory through four theoretical propositions centred on the role of BAs. The proposition highlights how BAs relationship management, tacit knowledge sharing, task mental models and transactive memory are key contributors of ASD teams' DC. The study also found that BAs contribute to ASD teams' ability to embrace agile principles 2, 4, 6 and 12. This study can inform the design of capacity development programmes for individual team members and BAs and thus help managers curate teams that will best promote DC.

This study can inform the design of capacity development programmes for individual team members and BAs and thus help managers curate teams that will best promote DC.

This study builds on the relatively few studies which focus on DC within software development (SD) teams and ASD project teams. Moreover, the study explores how an individual (i.e. a BA) can contribute to the DC of a team.

In software development (SD), practitioners have realized the importance of lean thinking. A new term “Leagile” is coined, which is an integrated approach of traditional lean and agile thinking to managing the operations. The study aims to investigate the application of the Leagile principles in a new sector and establish a relationship between the adoption of Leagile approach and operational performance (OP) in SD organizations.

Empirical research is conducted to investigate the linkage between the Leagile principles and operational measures. Data is collected through surveys from 256 SD industries located in 11 states of India and analysed using the structural equation modelling approach.

The practitioners envisage a positive impact of adoption of Leagile principles on OP of SD organizations, but one of the principles, i.e. perfection, is unable to influence the performance.

The study contributes by authorizing the contribution of Leagile principles towards OP of SD organizations. The outcomes will motivate the practitioners to enhance the adoption of Leagile principles in SD organizations.

This study aims to examine the impact of two dimensions of agile work practices (i.e. agile taskwork and agile teamwork) on team efficacy and creativity. Further, it examines the mediating effect of team efficacy in the relationship between two dimensions of agile work practices and team creativity.

The data were collected from 563 professionals working in 290 information technology (IT) companies in India using a self-reporting structured questionnaire. Partial least squares-structural equation modeling (PLS-SEM) was used to test the hypothesized model.

The results demonstrate that agile taskwork and agile teamwork positively impact team creativity and team efficacy, and team efficacy positively impacts team creativity. Furthermore, team efficacy partially mediates the impact of agile taskwork and agile teamwork on team creativity.

This study shows the importance of agile work practices and team efficacy to enhance team creativity. The research offers managers strategies to boost team creativity.

There is a dearth of research examining the distinct effects of agile taskwork and agile teamwork on team efficacy and team creativity. Also, this study is one of its kind that examines the mediating mechanisms that explain the effect of agile taskwork and agile teamwork on team creativity.

This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.

This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.

The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.

Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.

Today’s unpredictable and fast-changing work environment challenges researchers and organizations to rethink learning. In contrast to traditional learning designs, new learning frameworks such as agile learning are more learner centered, integrated into the workplace and socially shaped. The purpose of this study is to examine Working Out Loud (WOL) as an agile learning method.

This intervention study used a pre–post and six-month follow-up design (N = 507) to evaluate the effects of WOL on learners’ vigor (affective outcome), WOL behavior (behavioral outcome) and psychological empowerment (cognitive outcome) at work.

The authors compared the three longitudinal measurements using multilevel modeling. Results revealed that WOL could significantly increase learners’ WOL behavior and psychological empowerment at work in the post and six-month follow-up measurements. No effect was found on learners’ vigor at work.

This study highlights the need for research on new, more agile learning frameworks and discusses their relevance to the literature. Agile learning frameworks enable learners to be more autonomous and flexible, allowing them to better adapt to changing environmental demands.