Search results

The purpose of this paper is to use translation theory to develop a framework (called FTRA) that explains how companies adopt agile methods in a discourse of fragmentation and articulation.

A qualitative multiple case study of six firms using the Scrum agile methodology. Data were collected using mixed methods and analyzed using three progressive coding cycles and analytic induction.

In practice, people translate agile methods for local settings by choosing fragments of the method and continuously re-articulating them according to the exact needs of the time and place. The authors coded the fragments as technological rules that share relationships within a framework spanning two dimensions: static-dynamic and actor-artifact.

For consistency, the six cases intentionally represent one instance of agile methodology (Scrum). This limits the confidence that the framework is suitable for other kinds of methodologies.

The FTRA framework and the technological rules are promising for use in practice as a prescriptive or even normative frame for governing methodology adaptation.

Framing agile adaption with translation theory surfaces how the discourse between translocal (global) and local practice yields the social construction of agile methods. This result contrasts the more functionalist engineering perspective and privileges changeability over performance.

The use of translation theory and the FTRA framework to explain how agile adaptation (in particular Scrum) emerges continuously in a process where method fragments are articulated and re-articulated to momentarily suit the local setting. Complete agility that rapidly and elegantly changes its own environment must, as a concomitant, rapidly and elegantly change itself. This understanding also elaborates translation theory by explaining how the articulation and re-articulation of ideas embody the means by which ideas travel in practice.

While the choices available for project management methodologies have increased significantly, questions remain on whether project managers fully consider their alternatives. When project categorization systems and criteria are not logically matched with project objectives, characteristics and environment, this may provide the key reason for why many software projects are reported to fail to deliver on time, budget or do not give value to the client. The purpose of this paper is to identify and categorize critical success factors (CSFs) and develop a contingency fit model contrasting perspectives of traditional plan-based and agile methodologies.

By systematically reviewing the previous literature, a total of 37 CSFs for software development projects are identified from 148 articles, and then categorized into three major CSFs: organizational, team and customer factors. A contingency fit model augments this by highlighting the necessity to match project characteristics and project management methodology to these CSFs.

Within the three major categories of CSFs, individual factors are ranked based on how frequently they have been cited in previous studies, overall as well as across the two main project management methodologies (traditional, agile). Differences in these rankings as well as mixed empirical support suggest that previous research may not have adequately theorized when particular CSFs will affect project success and lend support for the hypothesized contingency model between CSFs, project characteristics and project success criteria.

This research is conceptual and meta-analytic in its focus. A crucial task for future research should be to test the contingency fit model developed using empirical data. There is no broad consensus among researchers and practitioners in categorizing CSFs for software development projects. However, through an extensive search and analysis of the literature on CSFs for software development projects, the research provides greater clarity on the categories of CSFs and how their direct, indirect and moderated effects on project success can be modelled.

This study proposes a contingency fit model and contributes towards developing a theory for assessing the role of CSFs for project success. While future empirical testing of this conceptual model is essential, it provides an initial step for guiding quantitative data collection, specifies detailed empirical analysis for comparative studies, and is likely to improve clarity in debate. Since previous studies have not rigorously assessed the impact of fit between project characteristics, project environment and project management methodology on project success, additional empirically robust studies will help to clarify contradictory findings that have limited theory development for CSFs of software development projects to date.

Previous research for software development projects has frequently not fully incorporated contingency as moderation or contingency as fit (traditional vs agile). This research sets out to develop fully a contingency fit perspective on software development project success, through contrasting traditional plan-driven and agile methodologies. To do this, the paper systematically identifies and ranks 37 CSFs for software projects from 148 journal publications and holistically categorizes them as organizational, team, customer and project factors.

Aligning the project management methodology (PMM) to a particular project is considered to be essential for project success. Many outsourced software projects fail to deliver on time, budget or do not give value to the client due to inappropriate choice of a PMM. Despite the increasing range of available choices, project managers frequently fail to seriously consider their alternatives. They tend to narrowly tailor project categorization systems and categorization criterion is often not logically linked with project objectives. The purpose of this paper is to develop and test a contingency fit model comparing the differences between critical success factors (CSFs) for outsourced software development projects in the current context of traditional plan-based and agile methodologies.

A theoretical model and 54 hypotheses were developed from a literature review. An online Qualtrics survey was used to collect data to test the proposed model. The survey was administered to a large sample of senior software project managers and practitioners who were involved in international outsourced software development projects across the globe with 984 valid responses.

Results indicate that various CSFs differ significantly across agile and traditional plan-based methodologies, and in different ways for various project success measures.

This study is cross-sectional in nature and data for all variables were obtained from the same sources, meaning that common method bias remains a potential threat. Further refinement of the instrument using different sources of data for variables and future replication using longitudinal approach is highly recommended.

Practical implications of these results suggest project managers should tailor PMMs according to various organizational, team, customer and project factors to reduce project failure rates.

Unlike previous studies this paper develops and empirically validates a contingency fit model comparing the differences between CSFs for outsourced software development projects in the context of PMMs.

The application of agility principles and methodologies on Enterprise Architecture (EA) is a promising field. This paper aims to provide an in-depth study of the Agile Enterprise Architecture (AEA) by studying EA practitioners’ perspectives to propose a foundational framework for AEA.

The authors formulate a foundational framework that defines the AEA motivators, enablers and blockers using the agile manifesto as one of the AEA enablers where a total of 156 EA stakeholders with at least one year of experience in enterprise architecture were surveyed, and a set of hypotheses was analyzed and tested based on the proposed framework. The authors also develop a quantitative method to evaluate the agility index of the EA based on the introduced framework.

The research results show with significance that enterprise architects perceive positively the application of the agility methodologies on the enterprise architecture. This perception is primarily affected by the enterprise size, the EA dependency and the agile methodologies awareness. The findings also indicate that AEA is primarily motivated by the Business and IT Change Ready and Responsive EA. Finally, an EA Agility Index (EAAI) was designed to assess the agility application of the EA based on the three forces, i.e. motivators, enablers and blockers.

Because of the chosen research approach and the sample size, the research results may lack generalizability. Also, EAAI designed was not thoroughly tested.

The paper includes implications for the design and development of an EA Agility Index, and the need to increase the awareness of the agility methodologies to overcome the blocker of the unfamiliarity with the agile methodologies implying that the current business models in enterprise must be more aligned with the agile methodologies.

While there are efforts to develop AEA frameworks, one of the major findings of the literature review conducted is that there is evident research gap in the literature on the perception and associated factors of the EA stakeholders on having an agile enterprise architecture. This paper attempts to fill this gap.

This paper aims to assess the combined application of Lean Six Sigma and agile approach for optimizing operational processes of order management in the seed industry.

This study is based on an action research case conducted in a multinational Brazilian Seeds Business enterprise. This paper reports on the application of the Lean Six Sigma define-measure-analyze-improve-control (DMAIC), using the steps of DMAIC cycle as a sprint of agile approach. The methodology involves outlining an operational process through sequential activities, each associated with a cycle time, equivalent number of full-time employee and number of orders. Performance metrics for the order management process include continuous monitoring of these activities, using monitoring systems, management software and manual records to collect data.

The findings reveal significant improvements in critical-to-quality measures related to customer care, planning and logistics. The implementation of the DMAIC methodology and agile approach resulted in tangible enhancements in cycle time, defects per opportunities and overall process efficiency. The results allow the classification of defects, the identification of their causes and, consequently, the presentation of a control plan to mitigate these problems. Furthermore, the study identifies key causes of operational issues and proposes a prioritized action plan.

The limitation of this research is its restriction to a single case. The external validity of the results and generalizability to other organizational contexts may be compromised due to the lack of case diversity. The fact that the research focuses on a single company, even if it is a large multinational company, may limit the applicability of the findings to different sectors, sizes and organizational structures, which may be an opportunity for future research.

The findings suggest that the integrated approach of DMAIC and agile methodology contributes to a culture of continuous improvement and operational efficiency. The systematic collection and analysis of data enhance evidence-based decision-making, providing a robust foundation for strategic and operational choices. Moreover, the successful integration of methodologies presents a comprehensive framework applicable to diverse organizational challenges.

The paper applies action research to understand and address operational challenges, emphasizing practical solutions. The integration of DMAIC and agile enhances the depth of process analysis, enabling the identification, implementation and control of improvements. This study offers a significant contribution both to practitioners, providing practical implications, and to academics, enriching the Lean Six Sigma and agile body of knowledge.

Agile methodologies are widely used to manage the technical complexity of software development, and project governance can provide feasible means of organizational support for complex project success. The purpose of this paper is to: analyze the project governance practices of public sector organizations, illustrate what kind of impact these practices have on agile software projects and describe the tensions of agile project governance.

The research is based on qualitative research strategy and applies elaborative logic with analyses of three case projects in the Finnish public sector.

The findings of the research describe how project governance practices can be categorized into six dimensions: business case, contracting, controlling, steering, decision-making and capability building. The results illustrate how these practices either support or detract the performance of agile projects. The results also show that there are two interfaces to agile project that create most tensions to governance – the public sector and technology.

The study contributes to both project management and information and communication technology theories by combining technical aspects of agile methodologies with micro-level project governance practices. The study also adds original value to academics by introducing the new concept of “agile project governance.” The results of this study will allow public sector project organizations to design appropriate governance mechanisms for agile projects, and to identify the challenges and tensions that need to be considered and managed in the process.

The aim of the article is to define the way of understanding of agile in enterprises, to verify the factors limiting agility implementation, as well as to understand what the expectations of enterprise management towards agile implementation are.

The article uses both literature studies and empirical research. The research was conducted in 2019 in 152 companies located in Luxemburg, Croatia and Poland, which have implemented an agile approach to management.

In most of the surveyed organisations, agile is understood as a methodology for creating projects or applications. The most common barriers to implementing agile in the surveyed enterprises are culture too deeply rooted in traditional methodologies and the lack of funds to introduce transformations. Growth in productivity and competitiveness and reducing delivery time stand out among the most common expectations of the management of the surveyed enterprises.

The article is in line with the idea of analysing the key factors of a successful agile implementation, which can be a guideline for an enterprise to manage the adoption of agility. The article utilises original research tools, provides comparisons between countries and presents implications for practitioners and researchers.

The purpose of this paper is to demonstrate how agile project management can foster creativity in project teams.

The study is based on an extensive literature review of agile project management and team creativity and is matching these two to answer the following research questions: (1) how agile project management approach can foster creativity in project teams? and (2) which principles and practices promoted by the most popular agile methodologies enhance creativity in project teams?

Five creativity-conducive spaces in agile project management were identified and integrated into a conceptual framework, namely, a space for generative social interactions, a space for learning, a space for change and adaptation, a space for exploration and a space promoting team members' well-being. In the next step, based on a thorough analysis of seven widespread agile project management methods, a large number of agile principles and practices were mapped into each of the five conceptual spaces.

This study provides new insights into how agile project management can foster creativity in project teams. The conceptual framework developed in this paper might be utilized to enhance creativity in agile teams, it can also serve as a starting point for future research.

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.

Security in large-scale agile is a crucial aspect that should be carefully addressed to ensure the protection of sensitive data, systems and user privacy. This study aims to identify and characterize the security practices that can be applied in managing large-scale agile projects.

A qualitative study is carried out through 18 interviews with 6 software development companies based in Portugal. Professionals who play the roles of Product Owner, Scrum Master and Scrum Member were interviewed. A thematic analysis was applied to identify deductive and inductive security practices.

The findings identified a total of 15 security practices, of which 8 are deductive themes and 7 are inductive. Most common security practices in large-scale agile include penetration testing, sensitive data management, automated testing, threat modeling and the implementation of a DevSecOps approach.

The results of this study extend the knowledge about large-scale security practices and offer relevant practical contributions for organizations that are migrating to large-scale agile environments. By incorporating security practices at every stage of the agile development lifecycle and fostering a security-conscious culture, organizations can effectively address security challenges in large-scale agile environments.