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

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

• Journal of Internet Computing and Services
• /
• v.15 no.1
• /
• pp.13-27
• /
• 2014

Agile methodologies have gained recognition as efficient development processes through their quick delivery of software, even under time constraints. However, like other agile methods such as Scrum, Extreme Programming (XP) and The Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD) has been criticized due to the unavailability of security elements in its twelve practices. In order to examine this matter more closely, we conducted a systematic literature review (SLR) and studied literature for the years 2001-2012. Our findings highlight that, in its current form, the FDD model partially supports the development of secure software. However, there is little research on this topic, as detailed information about the usage of secure software is rarely published. Thus, we have been able to conclude that the existing five phases of FDD have not been enough to develop secure software until recently. For this reason, security-based phase and practices in FDD need to be proposed.

• International Journal of Contents
• /
• v.12 no.3
• /
• pp.29-33
• /
• 2016

Cloud computing makes extensive use of virtual machines that permit for workloads, as well as resource usage, to be isolated from one another, and a hypervisor can be used by a virtual machine to construct cloud computing infrastructure. However, the hypervisor has high resource usage when constructing virtual machines, which results in a waste of allocated resources when not activated. Docker provides a more light-weight method to obtain agile computing resources based on a container technique that handles this problem. In this study, we have chosen this specific tool due to the increasing popularity of MapReduce and cloud container technologies such as Docker. This study aims to automatically configure Twister workloads for container-driven clouds. Basically, this is the first attempt towards automatic configuration of Twister jobs on a container-based cloud platform VM for many workloads.

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

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

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

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