• International Journal of Computer Science & Network Security
• /
• v.24 no.8
• /
• pp.145-152
• /
• 2024

Agile project management is an ongoing method to project completion that actually took place all across length of the project's life cycle. Because loop allows you to adapt as you go rather than maintaining a linear route, iterative methods are mainly applied in software development to ensure velocity and agility. Many pitfalls abound in agile software development adaptations that organizations fail to sidestep. New competitive challenges, fluctuating market dynamics, technological disruption, and the ever-changing demands of empowered customers confront organizations around the world. Organizations are all under tremendous pressure to adapt to change and deliver good products and services to customers more swiftly. Research measured at the challenges that could be encountered and offered advice for how agile development might flourish as it becomes a component of a company's family. Our paper gives a comprehensive review of the most significant obstacles that companies encounter while adopting agile techniques. Adaptability. The agile approach encompasses a variety of techniques, which each have different usage in various sectors. Because certain other standards existing today clash with agile methodology, the adaptation of any of the agile techniques in work environments posed a problem. In this paper, we will cover some of the challenges that firms face in adopting the agile software development life cycle.

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

• Journal of Information Processing Systems
• /
• v.9 no.1
• /
• pp.69-88
• /
• 2013

Agile methods are highly attractive for small projects, but no agile method works well as a standalone system. Therefore, some adaption or customization is always required. In this paper, the Agile Framework for Small Projects (AFSP) was applied to four industry cases. The AFSP provides a structured way for software organizations to adopt agile practices and evaluate the results. The framework includes an extended Scrum process and agile practices, which are based on agility and critical success factors in agile software projects that are selected from Scrum, XP, FDD, DSDM and Crystal Clear. AFSP also helps software managers and developers effectively use agile engineering techniques throughout the software development lifecycle. The case study projects were evaluated on the basis of risk-based agility factors, the agility of the adopted practices, agile adoption levels, and the degree of the agile project success. The analysis of the results showed that the framework used in the aforementioned cases was effective.

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

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

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

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

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

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

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