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

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

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

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

• International Journal of Computer Science & Network Security
• /
• v.24 no.5
• /
• pp.103-110
• /
• 2024

In the quickly developing world, the idea of the conventional advancement needs to advance[1]. When applied to the advanced work environment, the conventional strategies give as much damage as they do great. Tragically, an absence of versatility in the customary techniques has prompted an inflexible work structure that is truly not viable with the present business. The Agile technique is, subsequently, a more adequate practice, in view of creating programming at a faster speed, while as yet looking after proficiency. The coordinated programming improvement strategies are concentrated in this paper. As per study results, Agile software development group needs solid client association; great light-footed task the executives' measures; item proprietor expands business esteem conveyed by group and need and draw in partners; great deft designing procedures or practices; and great advancements and advancement apparatuses[2]. This examination has suggestions for positive social change since associations that comprehend the basic components might have the option to improve project the executives' systems and money saving advantages prompting higher effectiveness, productivity, and efficiency hence profiting the board, representatives, and client. This survey paper incorporates various methodologies of Agile and their analysis.

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

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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.2
• /
• pp.646-663
• /
• 2014

Scrum is one of the most popular and efficient agile development methods. However, like other agile methods such as Extreme Programming (XP), Feature Driven Development (FDD), and the Dynamic Systems Development Method (DSDM), Scrum has been criticized because of lack of support to develop secure software. Thus, in 2011, we published research proposing the idea of a security backlog (SB). This paper represents the continuation of our previous research, with a focus on the evaluation in industry-based case study. Our findings highlight an improved agility in Scrum after the integration of SB. Furthermore, secure software can be developed quickly, even in situations involving requirement changes of software. Based on our experimental findings, we noticed that, when integrating SB, it is quite feasible to develop secure software using an agile Scrum model.

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