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

• Journal of Digital Convergence
• /
• v.13 no.12
• /
• pp.171-177
• /
• 2015

The aim of the study is to introduce a software reuse technique into a generalized agile process for a reuse of a product backlog item. The software engineering community has made some efforts to integrate software reuse and agile methods. Most studies have emphasized the use of agile practices in software product line engineering, whereas reuse in agile methods has received little focus. Nevertheless, the activities and artifacts that provided by an agile method exhibit characteristics that promote reuse. In this paper, we identify catalytic activities and characteristics that promote reuse in a generalized agile process, and we suggest a reuse technique for a product backlog item. Based on our results, we integrate a backlog factoring technique into a generalized agile process for reuse. In addition, we apply the proposed technique and demonstrate a prototype of backlog item reuse in agile methods for a restaurant chain 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.

• International Journal of Internet, Broadcasting and Communication
• /
• v.8 no.3
• /
• pp.78-91
• /
• 2016

Various studies have proven that human is the biggest challenge in the process of transitioning to agile. Culture and mindset are two critical elements of human factors causing issues in agile environment. This study involved thirty-two (32) agile practitioners from nineteen (19) country to validate the issues from human factors. The purpose of the study is to discover human factors that required more attention and factors that give a low impact on the agile environment. Furthermore, this paper presents research analysis on some of popular human factors such as collaboration, hierarchy, communication and other critical factors which company may face. The results of this analysis can be used as a guide for IT organization to consider the critical challenges they may encounter.

• 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 the Korean Society of Systems Engineering
• /
• v.6 no.2
• /
• pp.47-57
• /
• 2010

Taylor and Ford in the 1910s led to the "scientific management" for the entire industry from the manufacturing spread of TQM Total Quality Management has been structured as a management efficiency, such as 6-Sigma techniques were developed. SW development also introduces the idea, such as CMMI and SPICE-based process management, management practices have evolved. However, in recent years to increase the knowledge of workers in the manufacturing process oriented management approach is under serious challenge. Business performance or productivity will be varied depending all motivation, human relationship, job involvement rather than simply putting a lot of time. Especially in the SW industry which is depending on human resource, Creativity should be limited in traditional management methods. Recently, Google and Apple, Cisco and global advanced companies adopt a human relationship management. Their productivity and creativity in product development has been successful by giving autonomy and motivation, enthusiasm and vision to tile employees. Human relationship management since the mid-1990s, appears as a new paradigm so called Agile process in the field of SW development. Agile processes emphasis on light, flexible and responding to changes immediately in the business environment step away from traditional management approach which is the heavy and complicated process. In this paper, agile project management concepts and practices which is applied to industry will be examined.

• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.67-74
• /
• 2016

Distributed agile software development faces difficulties for instance lack of visibility across development and delivery processes, complex and disjointed development processes, inability to capitalize on business opportunities, lack of communication agility between disconnected owners, development teams, and users or clients. However these difficulties are solved with the help of cloud computing services. This study proposes a framework to provide a skeletal or structural environment for distributed agile software development in cloud computing environment. The framework guide towards the best tooling to deliver a consistent, automated, governed, and unified agile software development process with reduced technical debt, and minimized project backlog. In addition to this, the study highlights the benefits of cloud computing in agile software development.

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

• KIPS Transactions on Software and Data Engineering
• /
• v.9 no.7
• /
• pp.213-220
• /
• 2020

The convolutional neural network is composed of convolutional layers and fully connected layers. The nonlinear activation function is used in each layer of the convolutional layer and the fully connected layer. The activation function being used in a neural network is a function that simulates the method of transmitting information in a neuron that can transmit a signal and not send a signal if the input signal is above a certain criterion when transmitting a signal between neurons. The conventional activation function does not have a relationship with the loss function, so the process of finding the optimal solution is slow. In order to improve this, an agile activation function that generalizes the activation function is proposed. The agile activation function can improve the performance of the deep neural network in a way that selects the optimal agile parameter through the learning process using the primary differential coefficient of the loss function for the agile parameter in the backpropagation process. Through the MNIST classification problem, we have identified that agile activation functions have superior performance over conventional activation functions.

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