• Journal of Advanced Navigation Technology
• /
• v.17 no.3
• /
• pp.346-353
• /
• 2013

The dominant trend in software development is the globalisation of the software industry. This development is faced with diverse problems, which require solution by the adoption of new processes and development techniques. eXtreme Programming (known as XP) is one methodology which is now at the leading edge of software development. This recent trend in XP allows organisation members to cooperate towards the development of new software independently of the existing developers. This is achieved functionally between the members by the development of distributed pair programming, this is not IDE plug-in shape of text, simple screen sharing or chatting function based.

• Journal of Internet Computing and Services
• /
• v.9 no.6
• /
• pp.155-163
• /
• 2008

Project Monitoring and Control is one of the required activities in project management. This activity provides the information about whether a project is making a progress as it is planned. It is usually performed in weekly meetings or milestone meetings where the project manager checks the project's current status based on project measures such as schedule, cost and work performance. One of the popular method for project monitoring and control is EVM(Earned Value Management). The major characteristic of EVM is that it uses only one measure 'cost' for schedule and work performance so that it enables 2 independent graphs to be illustrated in one integrated graph based on cost. For applying EVM to a project, it is essential to break whole work to work packages and to assign value of cost to each work package at the initial stage of the project. Therefore EVM is well matched with the lifecycle which requires whole plan at the beginning of project. However, in XP(eXtreme Programming), whole customer requirements are difficult to define and to make a complete plan at the beginning and are more detailed in each Iteration. Therefore EVM is not comfortable method for XP. Therefore in this research we suggest 3 layer EVM which can be applied in XP, and develop a process guidelines based on CMMI(Capability Maturity Model Integration) PMC(Project Monitoring and Control) process area.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.577-579
• /
• 2001

eXtreme Programming(이하 XP)은 프로젝트를 수행하는 데에 있어서 흔하게 발생하는 위험 요인들을 Light-weight 한 방법으로 해결하기 위한 방법론이다. XP 개발 방법론은 개발 주기의 단위를 작게 나누어서 피드백을 받는 기간을 짧게 잡았다는 점과, Pair Programming 방법을 도입했다는 점, 개발 과정에서의 고객의 비중을 높이고, 다양한 모듈 테스트/기능 테스트를 통해서 제품의 오류를 최소화 했다는 점 등의 특징을 갖고 있다. 그러나 XP는 소규모의 개발팀일 경우에만 그 효용성이 입증되고 있으며, 수많은 테스트 과정과 개발의 전과정에서의 고객의 적극적인 참여의 요구는 생산 비용면에서나 고객의 부담에 있어서 단점으로 여겨지고 있다. 따라서 본 고에서는 이러한 점들을 보완하기 위한 몇 가지 방안과 더불어 우리나라의 개발 환경에 효과적으로 적용하기 위한 방안을 제시하고자 한다.

• Journal of Internet Computing and Services
• /
• v.9 no.2
• /
• pp.107-118
• /
• 2008

The XP, the representative methodology of Agile software development, maximizes the effectiveness of the development by focusing on development itself and using primitive and basic process definition that can be easily implemented in the fields. However, the most of XP's practices came from those of engineering and the manogement practices of work product tend to be overlooked. The research on the implementation of those manogement practices has not been performed enough. Because of deficiency of processes that guide the change control over major baselines of work product and that describe proper continuous integration and refactoring in XP, the integrity of those work products is difficult to be guaranteed. To fulfill this work product integrity, CM(configuration manogement) should be hired and CMMI(Capability Maturity Model Integration) is considered to be the best references for that purpose, CMMI defines the required practices of CM and leave implementation details to the organization so that it could customize those practices based on the characteristics of its development methods. The CM process implementation guidelines based on CMMI could provides work product integrity with a way of keeping XP's agility that includes continuous integration, refactoring and small release. In this research, we selected CM process factors applicable to XP among CMMI's CM practices and based on them we developed the CM implementation guidelines.

• Journal of Internet Computing and Services
• /
• v.16 no.5
• /
• pp.87-92
• /
• 2015

Numerous IT organizations and companies around the world aspire to improve the efficiency and general standard of their software development. The IT organizations want to seize the opportunities and take advantages of new development processes and methodologies. These advantages include higher customers' satisfaction and better software quality among many. In order to achieve them, different agile software methodologies such as scrum, Feature driven development, eXtremeProgramming (XP), Dynamic system development method, Kanban and others have been frequently adopted by IT organizations across the world. Several studies have shown that agile software development methods are effective in a lot of settings. This study, in which 40 agile practitioners from Malaysia participated, additionally confirms the effectiveness of agile development methods. Furthermore, this paper presents some of the critical barriers not well-known by IT-organizations. The results of this analysis can be used to guide IT organization from the obstacles they may face while adopting agile in their environments.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.9 no.8
• /
• pp.3231-3248
• /
• 2015

Many IT organizations aspire to improve the efficiency and general standard of their software development effort by implementing agile software development practices. Some of the popular agile development methods adopted by IT organizations are Scrum, eXtreme Programming (XP), Kanban, Featured Driven Development (FDD) and Dynamic System Development Method (DSDM). This paper intends to identify and analyze the barriers that impact on the performance of IT organizations that use such agile software development methods. The analysis will help the IT organizations to cater the needed aspects to be successful. The analysis will also help the IT organizations to select the right methodology for their organization. The contribution of this analysis is to present guideline related to avoid or overcome the barriers towards adoption of agile.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.469-471
• /
• 2004

소프트웨어 생명주기 동안 변화하는 요구사항을 관리하기 위하여 다양한 기법들이 등장하고 있다. XP(eXtreme Programming) 기법에서 사용되는 유저 스토리는 고객이 시스템 관련 표현들에 대한 부담을 가지지 않고 자신의 요구사항을 표현할 수 있다는 장점을 가지고 있지만 그런 반면 체계를 가진 정형화된 문서가 아니고 일상적인 용어로 기술된다는 점 때문에 XP 기법에 대한 이해가 없는 타부서나 개발 관계자들과의 요구사항에 관한 문서 교환 시 문제가 발생한다. 본 고에서는 이 문제를 해결하기 위한 방안으로 유저 스토리로부터 유즈케이스를 모델링 하는 방법을 제안하였으며, 제안된 방법을 검증하기 위하여 XP 기법을 사용하여 진행된 DVD 타이틀 대여 웹사이트 개발 프로젝트에 적용한 사례를 분석하였다.

• 한국IT서비스학회:학술대회논문집
• /
• 2010.05a
• /
• pp.529-535
• /
• 2010

오늘날의 엔터프라이즈 IT 환경은 비즈니스 요구사항이 빠르게 변하면서 기존 시스템들의 민첩한 대응이 어렵고, 비즈니스 프로세스가 점점 복잡해지면서 시스템 개발 및 제어가 힘든 상황이다. 이 때문에 관리비용은 점점 증가하고 시스템의 수명주기가 단축되면서 전체적인 개발생산성이 낮아지고 있다. 최근 이와 같은 소프트웨어 개발문제를 극복하기 위해서 XP(eXtreme Programming)와 SCRUM 같은 애자일(agile) 방법론이 등장하게 되었고, 점차 대규모의 엔터프라이즈 어플리케이션 개발에 적용할 필요성이 대두되고 있다. 따라서 본 논문에서는 엔터프라이즈 어플리케이션의 개발생산성을 향상시키고 수명주기를 연장시키는데 효과적인 ISIS(Integrated System of Independent Sub-systems) 개발방법을 제안하고자 한다.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.15 no.6
• /
• pp.147-154
• /
• 2015

Recently agile development process became increasing effectiveness, quality, attention to experts in customer satisfaction, as evidenced in this methodology when selecting projects promoting productive efficiency. With regard to contemporary needs and user requirements on the methodology selected to meet this paper is the product based Cross functional team suggested methodology Feature Team model to solve problems of this model, and organizing the Cross functional team, this team but this outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-driven agile project through the Skills-based model and proposed a difference. And it examined the Agile Maturity metrics. PRINCE2 Agile Health-check entries future development direction of Agile techniques is a requirement of the project outset has studied the subject objective evaluation by the assumption that they can be changed at any time, not fixed this way and for the project team through research The proposed.

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