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

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

• 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 Korea Multimedia Society
• /
• v.20 no.4
• /
• pp.660-670
• /
• 2017

In case of auditing of the information system development project applying agile methodology, it is not appropriate to carry out a comprehensive check on the establishment of information system with only the existing check on software. This study considers the characteristics of the agile methodology in terms of Information System Auditing. To improve inspection quality of development project with agile methodology by deriving detailed check items of test activities at each stage, this study proposes a strategy to improve the check on software for the test activities of the supervisory model that is suitable for agile methodology, which emphasizes repetitive work.

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

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

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

• The KIPS Transactions:PartD
• /
• v.17D no.3
• /
• pp.203-208
• /
• 2010

This study improves the productivity of software development of open-market systems using agile methodology. The current processes of an open-market system are analyzed and inefficient processes are identified which are changed by applying the agile practice principles in Lean software. This study analyzes the process lead times and defects after the processes are changed to see the improvement effect.

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