• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.173-184
• /
• 2016

Prevalence of Agile methods in software companies is increasing dramatically. Software companies need to employ these methods to overcome the inherent challenges of traditional methods. However, transitioning to Agile approach is a topic of debate and there is no unique and well-defined transition model or framework yet. Although some research studies have addressed barriers and strengths behind the successful Agile deployment, it seems that this process still needs to be studied more in depth. The rationale behind this is the socio-technical nature of Agile transition and adoption. Particularly, the challenges and problems that software companies are facing during Agile transition, show that this process in more difficult than expected. Conducting a large-scale research study revealed that Agile transition and adoption process needs to be supported by several critical prerequisites. This study adopted a Ground Theory with the participation of 49 Agile experts from 13 different countries and empirically identified seven transition prerequisites. These prerequisites focus on the different aspects of the transition. The main aim of this paper is proposing these prerequisites and theoretical and practical implication of these prerequisites. Providing these prerequisites before moving to Agile increases chance of success in Agile transition and adoption and leads to fewer challenges during the change process.

• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.161-172
• /
• 2016

Agile software development methodology has been implemented by software industries over a decade ago and well accepted in the practitioner community. However, there is limited understanding on how agile practitioners aware towards implementation of agile practices in software development. Lack of awareness will lead to misunderstandings among agile practitioners and misuse the agile practices. In order to understand the awareness of agile practices, this paper aims to investigate the factors that affect awareness of agile practitioners in implementing agile practices. A systematic literature review (SLR)was conducted in order to classify and define the factors of awareness in agile software development methodology. The review was based on papers between 2002 and December 2014 from seven electronic databases. The relevant papers were included 20 journal articles, 24 conference papers,16 book chapters, 9 workshop papers. Consequently, 69 papers were identified that closely related with awareness in agile software development methodology. From the thematic analysis, 13 factors were classified from 42 elements. Based on the review result, understanding the influential factors on the awareness of agile practices will provide benefit to researchers and agile practitioners.

• Journal of Information Technology Services
• /
• v.20 no.2
• /
• pp.33-55
• /
• 2021

Many agile practices have been suggested for software development flexible enough to adapt to a rapidly changing environment. However, too many agile practices hinder computer engineers from deciding which agile practices are suitable for a given project. They need guidelines of the benefits an agile practice provides for a project, and how many of its benefits are effective. Therefore, this study investigates IT experts' perspectives on each agile practice's effectiveness in their projects using a repertory grid technique. Based on an analysis of data collected from 23 Korean IT experts about 33 agile projects, we elicit 361 cognitive effects categorized into 30 benefits using content analysis. Next, we identify agile practices that are primarily used and recognized as positive and further examine what benefits many agile practices usually bring. Finally, we evaluate the level of benefits overall that each agile practice provides.

• Journal of Information Processing Systems
• /
• v.9 no.1
• /
• pp.69-88
• /
• 2013

Agile methods are highly attractive for small projects, but no agile method works well as a standalone system. Therefore, some adaption or customization is always required. In this paper, the Agile Framework for Small Projects (AFSP) was applied to four industry cases. The AFSP provides a structured way for software organizations to adopt agile practices and evaluate the results. The framework includes an extended Scrum process and agile practices, which are based on agility and critical success factors in agile software projects that are selected from Scrum, XP, FDD, DSDM and Crystal Clear. AFSP also helps software managers and developers effectively use agile engineering techniques throughout the software development lifecycle. The case study projects were evaluated on the basis of risk-based agility factors, the agility of the adopted practices, agile adoption levels, and the degree of the agile project success. The analysis of the results showed that the framework used in the aforementioned cases was effective.

• International Journal of Internet, Broadcasting and Communication
• /
• v.8 no.3
• /
• pp.78-91
• /
• 2016

Various studies have proven that human is the biggest challenge in the process of transitioning to agile. Culture and mindset are two critical elements of human factors causing issues in agile environment. This study involved thirty-two (32) agile practitioners from nineteen (19) country to validate the issues from human factors. The purpose of the study is to discover human factors that required more attention and factors that give a low impact on the agile environment. Furthermore, this paper presents research analysis on some of popular human factors such as collaboration, hierarchy, communication and other critical factors which company may face. The results of this analysis can be used as a guide for IT organization to consider the critical challenges they may encounter.

• International Journal of Advanced Culture Technology
• /
• v.8 no.1
• /
• pp.82-88
• /
• 2020

In the face of recent digital and digital transformation, companies and industries are trying to be agile to adapt and respond to change. Agile paradigm is spreading beyond the boundaries of existing applications such as IT-related projects and software development. In this regard, this study, we analyzed the diffusion of agile paradigm by text mining abstracts of research papers from 2001 to 2019. In addition, we discussed agile transformation in the Fourth Industrial Revolution. Through this study, we confirmed that we are studying agile transformation in various fields such as business environment, corporate organizational culture, manufacturing industry, and supply chain. The results of this study will contribute to understanding the meaning and role of agile as a basic paradigm for digital transformation in the Fourth Industrial Revolution.

• International journal of advanced smart convergence
• /
• v.9 no.3
• /
• pp.59-70
• /
• 2020

There are many limitations in applying agile methodology to projects so far. In fact, projects overlap with other development methodologies and management processes, resulting in confusing progress, while there are often cases where the benefits of agile cannot be embraced due to a lack of understanding of agile processes and the organization's inability to adapt to change. It is an important role of information system development to improve the quality of agile application projects by discovering the problems and improvements in these cases. In this paper, we analyze the differences between existing development and project management methods and agile, and analyze agile processes. The optimal agile methodology was proposed by analyzing and applying methodologies established and applied mainly by large domestic development companies. In addition, the effectiveness was verified through a questionnaire of IT experts, and the result of the questionnaire was verified to be 4.75 points on a 5-point scale.

• KIISE Transactions on Computing Practices
• /
• v.23 no.7
• /
• pp.424-427
• /
• 2017

In an early stage, many people think that agile development methodology cannot be applied i large-scale IT projects. Nevertheless, agile development methodology has recently been introduced in variety of successful large-scale IT projects. In this paper, I compare two enterprise agile methodologies and introduce a case of Disciplined Agile Delivery (DAD) Framework, an enterprise agile development methodology. I compare and quantitatively measure the productivity of the development of two projects using Disciplined Agile Delivery framework and waterfall development methodology with a similar development scope.

• International Journal of Computer Science & Network Security
• /
• v.21 no.12spc
• /
• pp.586-596
• /
• 2021

Software organisations follow different methodologies for the development of software. The software development methodologies are mainly divided into two categories, including plan-driven and agile development. To attain project success, it is very significant to consider risk management during whole project. Agile development is considered risk-driven, but many risks are unreported at the industrial level. The risks can be divided into three categories, including (i) development risks, (ii) organisations risks, and (iii) people-oriented risks. This paper deals with Development risks specifically. Several risks related to development are faced by people working in the industry while dealing with agile development. Their management among the industry is a big issue, so this paper emphasises ARMF based on development-related risks by following agile development. This research work will help software organisations to prevent different project-related risks during agile development. The risks are elicited at two-level, (i) literature-based and (ii) IT industry based. A systematic literature review was performed for eliciting the agile risks from the literature. Detailed case studies and survey research methods were applied for eliciting risks from IT industry. Finally, we merged the agile development risks from literature with standard industrial risks. Hence, we established an agile risk mitigation framework ARMF based on agile development and present a groundwork established in light of empirical examination for extending it in future research.

• Journal of Digital Convergence
• /
• v.13 no.12
• /
• pp.171-177
• /
• 2015

The aim of the study is to introduce a software reuse technique into a generalized agile process for a reuse of a product backlog item. The software engineering community has made some efforts to integrate software reuse and agile methods. Most studies have emphasized the use of agile practices in software product line engineering, whereas reuse in agile methods has received little focus. Nevertheless, the activities and artifacts that provided by an agile method exhibit characteristics that promote reuse. In this paper, we identify catalytic activities and characteristics that promote reuse in a generalized agile process, and we suggest a reuse technique for a product backlog item. Based on our results, we integrate a backlog factoring technique into a generalized agile process for reuse. In addition, we apply the proposed technique and demonstrate a prototype of backlog item reuse in agile methods for a restaurant chain application.