• Journal of Intelligence and Information Systems
• /
• v.25 no.3
• /
• pp.141-160
• /
• 2019

Agile methodologies in software development, including the development of artificial intelligence software, have been widespread over the past several years. In spite of the popularity of agile methodologies in practice, there is a lack of empirical evidence to identify determinants of success of software projects in which agile methods are used. To understand the role of clients in software project where agile methods are used, we examine the effect of client-side factors, including lack of user involvement, unrealistic client expectations, and constant changes of requirements on project success from practitioners' perspective. Survey methods are used in this study. Data were collected by means of online survey to IT professionals who have experience with software development methodologies, and ordered logit regression is used to analyze the survey data. Results of our study imply the following managerial findings. First, user involvement is critical to project success to take advantage of agile methods. Second, it is interesting that, with an agile method, constant changes of client's requirements is not a negative factor but a positive factor of project success. Third, unrealistic client expectations do negatively affect project success even with agile methods.

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

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2019.07a
• /
• pp.305-306
• /
• 2019

대학의 게임개발 프로젝트는 학기라는 시간적 제약아래 게임 기획, 그래픽, 프로그래밍, QA 등 다양한 전공의 학생들이 팀을 이루고 진행한다. 게임 개발은 특성상 폭포수 개발과 같은 전통적인 개발방법론보다는 애자일 방법론이 보다 적합할 수 있다. 본 논문에서는 애자일 방법론 적용을 시도한 졸업작품팀의 개발자를 인터뷰하여 진행과정과 실패 요인에 대한 정보를 수집하여 분석하고, 애자일 방법론을 적용하기 위한 방안을 제시하였다.

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

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

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2015.05a
• /
• pp.78-81
• /
• 2015

소프트웨어 개발 환경의 급격한 변화와 지속적인 요구사항 변경으로 인해 발생하는 전통적 개발 방법론의 문제점을 해결하기 위한 애자일 개발방법론은 관심의 대상이 되었다. 비교적 짧은 주기를 가지고 요구사항 분석, 설계, 코딩, 테스트 과정을 끊임없이 반복하며 점차 소프트웨어의 규모를 늘려가는 애자일 개발방법은 오픈소스 소프트웨어의 개발방식(OSSDP)과 매우 유사하다고 볼 수 있다. 지금까지 애자일 방법론은 Scrum, XP, Lean, Crystal 방식 등 여러 가지 방법으로 시도 및 제안되고 있으며, 점차 다양한 프로젝트에서도 성공적으로 수행할 수 있도록 개선되고 있다. 이러한 애자일 개발방식의 특징을 OSSDP에 적용함으로써 더 많은 오픈소스 프로젝트가 성공할 수 있도록 하는 프로세스를 연구하는 것은 의미가 있다. 애자일 성명서에서 추구하는 4가지 가치인 소통, 단순성, 피드백, 용기를 반영한 관행(practice)을 OSSDP에 채택하여 추가할 경우, 사용자 만족도를 높이고 결과적으로 오픈소스 프로젝트 성숙도를 높이는데 기여할 것으로 기대한다.

• Aerospace Engineering and Technology
• /
• v.11 no.1
• /
• pp.111-117
• /
• 2012

Agile is a software development methodology which was established for four objectives; people, collaboration, responsiveness, and working software. Thus the Agile methodologies have been applied not only software development fields but also various special areas of technology. ESA (European Space Agency) adopt several Agile methodologies, including Scrum as the key technique, for the software development of ground segment. This article analyzes trends of Agile methodologies and introduction cases of the methodologies for ESA's ground segment software development.

• Information Systems Review
• /
• v.10 no.3
• /
• pp.185-205
• /
• 2008

As time to market and rapid reaction to changes in demand is much required, agile software development methodologies whose characteristics are great adaptability and short iteration developments are getting more popular. Though there have been a number of literature suggesting the great potential of agile software development, some recent studies have also mentioned its limitations. We believe there remains much confusion as to whether agile approaches are good to introduce or not. In an effort to provide 'real' characteristics of agile development, this paper evaluates Scrum, one of the most used agile approaches, using a software measurement framework. It also presents a Scrum measurement case study of a web portal company. We believe this study will provide some concrete guidelines as to whether Scrum is worth, what are weak points, and how to control the agile process in order to get over the weakness.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2014.11a
• /
• pp.617-620
• /
• 2014

프로그래밍 개발 시에 발생하는 위험요소로는 비용, 품질, 일정이 있다. 이와 같은 문제는 구현시에 발생하게 된다. 구현 중심의 개발방법론을 택하여 이러한 위험을 방지하기 위해 본 논문에서는 애자일 방법론을 적용하여 앱 개발을 수행했다. 앱 개발에 필요한 기능 추출 및 분석, 애자일을 적용한 짝 프로그래밍, 사용자 스토리, 스프린트 계획을 작성하였다. 애자일 방법론을 적용해 고객, 사용자, 개발자 간의 소통을 이끌어내 프로젝트의 성공률을 올리고 개발자간의 원활한 의사표현을 통해 복잡도가 높은 업무를 원활히 수행할 수 있도록 애자일 방법론을 적용하였다.

• Journal of Digital Convergence
• /
• v.11 no.8
• /
• pp.95-108
• /
• 2013

Agile development methods regards an interaction among software developers, operating softwares, and cooperation with customers as its main value. Most of the developing processes undergo a procedure called tailoring to meet the relevant project. Yet, in reality, projects run in disorder due to their overlap with other methods and management processes. As a result, the advantages of agile process cannot be fully used. So, the information system audit has an important role to detect these problems and improve the qualities of agile application projects. Also, researches should be conducted on Agile-based Iformation System Audit Model in order to enhance the effectiveness of agile projects. This paper suggests a model for an information system audit that applied agile developing methods. This model proposes audit domains and check lists for agile-based information system. In order to verify the suitability of the suggested model, more than 89.3% of the checklists were verified as suitable in all domains.