• Journal of the Korea Society of Computer and Information
• /
• v.16 no.11
• /
• pp.57-65
• /
• 2011

Since software reuse and agile development methods are seen as ways to shorten development time and accept frequent requirement changes, respectively, there has been growing interest and research on integrating these approaches. But despite the increasing number of software companies which have successfully adopted agile development methods, there has been little research on reuse in agile methods to further improve productivity. In this paper, we identify a new type of reuse asset and propose a task factoring technique by taking advantage of iteration characteristics to support reuse in agile software development methods. In addition, we can apply the proposed technique and show prototyping of task reuse in a video rental application.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.13 no.9
• /
• pp.4555-4571
• /
• 2019

Due to increasing interest in distributed agile software development, there is a need to systematically review the literature on challenges encountered in the agile software development environment. Using the Systematic Literature Review (SLR) approach, 32 relevant publications, dated between 2013 and 2018 were selected from four electronic databases. Data from these publications were extracted to identify the key challenges across the system development life cycle (SDLC) phases, which essentially are short phases in each agile-based iteration. 5 types of key challenges were identified as impacting the SDLC phases; these challenges are Communication, Coordination, Cooperation, Collaboration and Control. In the context of the SLDC phases, the Communication challenge was discussed the most often (79 times, 33%). The least discussed challenges were Cooperation and Collaboration (26 times, 11% each). The 5 challenges occur because of distances which occur in distributed environment. This SLR identified 4 types of distances which contribute to the occurrence of these key challenges - physical, temporal, social-cultural and knowledge/experience. Of the 32 publications, only 4 included research which proposed new solutions to address challenges in agile distributed software development. The authors of this article believe that the findings in this SLR are a resource for future research work to deepen the understanding of and to develop additional solutions to address the challenges in distributed agile software development.

• Journal of Information Technology Applications and Management
• /
• v.17 no.2
• /
• pp.1-18
• /
• 2010

The Agile methodology is a new trend in software development. Nowadays enterprises have been adopting the agile methodology in an effort to deal effectively with rapidly changing user requirements. In most cases, much improvement was accomplished in the software development. Some studies have mentioned that the motivation of software developers is a contributing factor on the improvement. However, it is not known yet what aspects of the agile methodology get them to be motivated. The aims of this study are the comparison between the traditional methodologies and agile methodology and look into potential motivation of software developer and their jobcharacteristics. For the empirical analyzing, research data were collected by 77 developers of 4 domestic IT companies. The analysis shows that there is significant differences on developer's potential motivation according to what kind of methodology is used. Agile developers to be more motivated than others methodologies developers. It also shows in detail that what kinds of job characteristics of developer are different among them depending on methodologies.

• Journal of Internet Computing and Services
• /
• v.15 no.1
• /
• pp.13-27
• /
• 2014

Agile methodologies have gained recognition as efficient development processes through their quick delivery of software, even under time constraints. However, like other agile methods such as Scrum, Extreme Programming (XP) and The Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD) has been criticized due to the unavailability of security elements in its twelve practices. In order to examine this matter more closely, we conducted a systematic literature review (SLR) and studied literature for the years 2001-2012. Our findings highlight that, in its current form, the FDD model partially supports the development of secure software. However, there is little research on this topic, as detailed information about the usage of secure software is rarely published. Thus, we have been able to conclude that the existing five phases of FDD have not been enough to develop secure software until recently. For this reason, security-based phase and practices in FDD need to be proposed.

• Journal of Information Technology Services
• /
• v.20 no.1
• /
• pp.41-54
• /
• 2021

The SW-centered battlefield management information system R&D project takes a long period of 5-10 years or more by applying a complex and rigid batch acquisition strategy. In order to solve this problem, it is necessary to institutionalize a rapid and flexible battlefield management information system R&D project management procedure applying agile development methodology, and a government project management organization and contract management method to support it In this study, we analyzed the case of applying the Agile development method centered on Scrum to the US SW-centered weapon system R&D project and the characteristics and problems of the battlefield management information system R&D project in Korea, and suggested improvement measures as follows. First, the battlefield management information system R&D model applies the hybrid development method, and the system requirements analysis and system structure design use the existing waterfall development procedure, and the agile method is applied from the SW requirements analysis to the system integration stage. Second, flexible adjustment of performance, schedule, and cost by organizing an Agile IPT in which military (requirements) - DAPA (project management) - developer - functional specialized organizations (test and evaluation, quality, government research institutes, etc.) participate. Third, improving the Basic Order Agreement so that it can be applied to agile R&D.

• 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 Digital Convergence
• /
• v.14 no.11
• /
• pp.297-304
• /
• 2016

The aim of the study is to combine software reuse with agile methods through reuse in the early stage of agile development. Although agile methods and software reuse have different practices and principles, these methods have common goals, such as reducing development time and costs and improving productivity. Both approaches are expected to serve as viable solutions to the demand for fast development or embracing requirement changes in the rapidly changing environments. In the present paper, we identify economical agile reuse and its type and study a reuse technique for input queue in Kanban board at the early stage of hybrid agile methods. Based on our results, we can integrate software reuse with agile methods by backlog factoring for input queue item in the hybrid Scrum and Kanban method. The proposed technique can be effectively applied to e-class applications and can reuse the input queue items, showing the combination of the two approaches. With this study, we intend to contribute to reuse in the early stage of agile development. In the future, we plan to develop a software tool for economical agile reuse.

• 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.

• 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.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.549-560
• /
• 2009

The Agile movement is a phenomenon that is part of the next phase of the software engineering evolution. At the same time, globally distributed software development is another trend delivering high-quality software to global users at lower costs. In this paper, Agile Framework for Distributed Software Development (AFDSD) has been suggested, and Chameleon project of Yahoo! Inc. has been implemented based on the framework. Also, the project has been evaluated by measuring Agile adoption and improvement levels, degrees of agility and agile project success, and comparing the performance and quality with the previous version. The overall performance and satisfaction with Chameleon increased by more than 30% since Agile techniques were adopted. Our objective is to highlight successful practices and suggest a framework to support adoption and evaluation of Agile techniques in a distributed environment.