Search results

Agile software development is an emerging approach in software engineering, initially proposed and promoted by a group of 17 software professionals who practice a set of “lightweight” methods, and share a common set of values of software development. They consolidated their thoughts, and defined these methods as “agile”. The approaches are based on experiences and best practices from the past by the above‐mentioned group of 17 software professionals. The purpose of this article is to outline the history and evolution of agile software development practices, their principles, and the criticisms as reported by the software development community.

A comprehensive literature review was undertaken to do this research.

Based on the literature review, this paper provides a comprehensive document that helps the practitioners working in the area of the agile software development.

This article will provide comprehensive material for the researchers in the area of agile software development. It will also be very useful for the practitioners practicing software development in the area of agile software development.

The objective of the study is to analyze the impact of the adoption of the Agile Mindset on the productivity of Agile software development teams in IT enterprises during COVID-19.

A web-based survey is performed with voluntary participants working with the Agile software development professionals with a specific focus on IT enterprises around Pune, India. For this the initial exploratory literature review was performed, to explore the team's behaviors and their response to the crises like the Covid-19 pandemic. Data is collected from the targeted population using the random sampling method. A questionnaire is designed with the help of a five-point Likert scale. All the respondents were analyzed based on their behaviors shown and how adopting to Agile mindset has impacted their productivity during the pandemic. Collected data would be then analyzed using the Smart PLS-SEM methodology.

Findings of the study show that Agile software development teams adopting to Agile mindset are better at responding to crisis and quick to adapt to change as teams adopting the Agile mindset is likely to sustain or even improve their productivity during the crises like Covid-19 pandemic. Adapting to an Agile mindset is important for Agile software development teams during a crisis as a response to changes in the working as well as environmental conditions. This study also shows that by adopting an Agile mindset, development teams are better at responding to the crisis eventually improving productivity.

Research limitations for this study-scope of the study could be extended to the larger population across geographies to have improved insights Productivity Factors like- Efforts Efficiency, Backlog-management Index (BMI), and Weighted Average Productivity (VWP) for team members can be included. More behavioral factors for Agile Mindset can be considered.

Agile software development teams are characterized by collaboration and responsibility. Recent enforcement of pandemic precautionary measures has enforced Agile software development teams to work remotely and maintain social distancing while in the office. It was challenging for most of the working people to adjust to the new working conditions (Yang et al., 2021) However, in IT organizations, adopting the Agile mindset has ensured continuous software deliveries, took ownership, and quickly adapted to the volatile situations, ultimately resulting into the growth in the productivity unlike to that of other sectors of the economy.

In this study, we have analyzed the hypotheses with statistical significance in association with constructs that are in sync with the available literature. Adopting the Agile mindset values has positively impacted the team's behavior resulting in productivity improvement even in the distributed working locations in pandemic situations.

The study highlights that adopting to Agile mindset has positively impacted an Agile software development team's productivity during the Covid-19 pandemic. As environmental conditions during Covid-19 were uncertain and ambiguous and teams were working in distributed and disconnected ways, many researchers have believed that it would have affected the overall productivity. This was turned true for most of the sectors of the economy, however, Agile software development teams have shown positive trends in their productivity, as they have adopted the Agile mindset values and principles, during crises.

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.

The purpose of this paper is to present the findings of Phase 1 of the research and to identify Australian agile software development organizations having such coexistence of agile and software configuration management (SCM) practices. This study employed “organization size” variable to study the phenomenon and used theory of Lean Thinking as a lens to analyse implementation variations of agile and SCM practices.

For this study, the research design was comprised of three phases. In Phase 1, a quantitative study using an online survey was performed to answer RQ using various statistical techniques. In Phase 2, an initial conceptual model based on a literature review was developed, and then a qualitative study was performed using one longitudinal case study. In Phase 3, another online survey was performed using various parametric statistical techniques to validate and generalize the findings of Phase 1 and 2 and the proposed SLAM traceability model. The scope of this paper is to discuss only Phase 1 and its associated findings.

The results of the analysis indicated that organizations, regardless of their size, frequently use agile practices for their software development operations. On the other hand, larger organizations use SCM practices comparatively more than medium and small organizations. However, traces of customized SCM process were found in most of the respondent (large, medium, and small) organizations, which indicates the coexistence of agile and SCM practices.

As there is no known listing or database available for such specialized criteria, a non-probabilistic sampling method was used, in the sense that the selection of members of the sample was arbitrary and subjective instead of a non-random selection from the pool of all agile practitioners in the field.

By using the quantitative method approach, this study aims to generate empirical evidence to contribute to the body of knowledge in the relevant areas. On the practical side, this research can also provide support to IT businesses in general, and software development organizations in particular, with the streamlining of the internal operational environment for the facilitation of an adaptable process and the resulting coexistence of value-added agile and SCM practices.

This paper aims to examine the link between information systems (IS) agility, HR performance management systems and job satisfaction using organizational information processing theory. The objective of this study answers the following questions: How does use of different IS agility impact HR systems and job satisfaction? What are the connecting pathways by which IS agility affects HR systems and job satisfaction?

The authors developed a theoretical framework based on the organizational information processing theory and collected primary data through an online-based questionnaire. Following these procedures, the authors analyzed the data using structural equation modeling (SEM).

SEM analysis of the data from 150 respondents supports the organizational information processing theory. The authors proposed eight hypotheses, and only one was rejected.

The data were collected from South Africa only, which is an emerging economy, and these cross-sectional data were gathered from the perspectives of the respondents.

The present paper empirically tests the conceptual model through the lens of organizational information processing theory.

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.

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.

Agile software development (ASD) is currently an emerging approach in software engineering for improving quality, initially advocated by a group of 17 software professionals who practice a set of “lightweight” methods, and share a common set of values of software development. Owing to the attractive claims of successes of the ASD approach, many traditional projects, which used to practice plan‐driven software development, are gradually transitioning into ASD‐based development. This paper seeks to report the results from a survey‐based ex‐post‐facto study aimed at determining the relative importance, if any, of the changes traditional plan‐driven software development projects have to undergo to adopt ASD practices.

The study was conducted using a web‐based survey with ASD practitioners who had experience of practicing plan‐driven software development in the past. ASD practitioners from a wide range of industrial sectors participated in the study. Similarly, the study is not restricted to any specific organisation/project size, culture, or nationality – the respondents were widely geographically distributed across continents.

The study received 241 responses, of which 165 were usable. The study did not reveal any substantial difference in importance of the four classes of changes hypothesised – changes in culture, changes in management style, changes in knowledge management strategy and changes in development processes. The authors believe that this is an important finding because it is indicative of not isolating one class of changes from another in practical transition exercises. However, another noteworthy observation was that transitioning from heavily process‐centric to short, iterative, test‐driven, and people‐centric development was considered by the largest percentage (roughly 77 per cent) of respondents to be very important. The open‐ended questions in the study also revealed three additional classes of changes: changes in personal characteristics, changes in customer attitude, and changes in knowledge and education of stakeholders.

In this work an attempt was made to gain an understanding of the relative importance of the different critical changes that would be helpful to a project manager who is involved in the transition from traditional plan‐driven software development practices to agile software development practices.

This paper aims to explore a case of customer and user participation in an agile software development project, which produced a tailor‐made information system for workplace support as a step towards a theory of participatory design in agile software development.

Based on an integrated framework for user participation derived from the participatory design literature the research was performed as a case study and semi‐structured, open‐ended interviews were conducted with about a third of the development team and with a representative sample of key players and future users in the customer organization. The interview data were supplemented with company and project documents.

The paper found genuine customer and user participation carried out by onsite customers and by other operational staff in the form of direct and indirect participation and with functional and democratic empowerment. The onsite customers played informative, consultative and participative roles. The analysis revealed that planning games, user stories and story cards, working software and acceptance tests structured the customer and user participation. This form of user participation supported a balance between flexibility and project progress and resulted in a project and a product which were considered a success by the customer and the development organization. The analysis showed that the integrative framework for user participation can also fruitfully be used in a new context to understand what participatory design is and how, when and where it can be performed as an instance of a design process in agile development. As such the paper contributes to an analytical and a design theory of participatory design in agile development. Furthermore the paper explicates why participatory design contributes to the successful completion of the investigated project. By drawing on innovation theory it was found that participatory design in agile development bears the characteristics of a successful organizational innovation. Grounding further explanations in complex adaptive systems theory the paper provides an additional argument why participatory design despite some identified challenges fosters project staff to successfully carry out the agile development project.

The paper presents an exploratory, empirical study of an understudied phenomenon and contributes to theory building.

The purpose of this study is to reflect upon the feasibility of agile methodologies, Scrum in particular, to supplement the procedural design and implementation of performance measurement systems (PMS).

The study is an interventionist case study that applied agile methodologies in the PMS development. Researchers actively participated in the PMS development, e.g. researchers designed some of the performance measurement prototypes in order to facilitate the agile development.

The study outlines an agile approach suitable for PMS development. The paper answers the topical needs for adaptability and agility in management accounting, by applying agile methodologies into PMS development. PMS development does not take place only as a project or process that systematically progresses from the measure selection to measure implementation. Instead, as the requirements for the PMS change during the development project, management may reject some measures and new measures emerge as the understanding about changing situations increase. Agile methodologies are a methodological way to respond to the inevitable change and to enhance management accounting adaptability.

This study contributes to the PMS literature by proposing that agile development methodologies can advance organizational features that increase management accounting adaptability. As a result, the study proposes a new approach for PMS development to supplement existing ones. Agile methodologies are especially suitable for extending the PMS in new, yet relatively immature areas of performance measurement. The new approach applies Scrum principles in PMS development. By drawing from the theories of performance measurement (system) development and enabling PMS, the paper furthers academic understanding about agile development of accounting information systems.

Companies can use the proposed approach in PMS development, particularly after the initial system implementation in redesigning the system. The approach may increase the PMS impact in organizations and prevent PMS implementation failures.

The paper identifies the potential of using agile methodologies to enhance PMS adaptability and provides preliminary evidence of the potential of such approach in supplementing processual PMS development frameworks.