Modeling Distributed Agile Software Development Utilizing Cloud Computing: A Holistic Framework

Distributed Teams ◽

Agile Development ◽

Computing Platform ◽

Agile Methodology ◽

Technological Advances ◽

In distributed agile software development, to conquer the problems raised by rapid development of complex products with ever changing technological advances and risks, there is a need of a model with specific tools and technology supported approaches to manage them. Distributed environment has challenges and complexities in many ways of over collocated teams. However, they seem to enhance the basic principles in which agile methodology thrives on. Agile projects and distributed projects are compatible and therefore practices, principles, tools, and techniques for distributed agile software development are introduced to the distributed teams to ensure that the agile projects become successful. Although cloud computing is well established for software system developments, its effect on agile methodology has not been extensively studied. This study outlines how agile projects can be modeled in the cloud-computing era, namely, seamless agile-cloud integration. We propose a model to improve Agile Methodology in distributed computing platform. This model has uncovered a gap between the distributed agile development phases that are overemphasized and the phases that require actual attention. In addition to this, emphasis on appropriate phases would help build desired software that can exploit the benefits of cloud computing in numerous ways.

Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective

Electronics ◽

10.3390/electronics10192341 ◽

2021 ◽

Vol 10 (19) ◽

pp. 2341

Author(s):

Rashid Ali Khan ◽

Muhammad Faisal Abrar ◽

Samad Baseer ◽

Muhammad Faran Majeed ◽

Muhammad Usman ◽

...

Keyword(s):

Scale Development ◽

Software Development ◽

User Satisfaction ◽

Large Scale ◽

Low Cost ◽

Rapid Development ◽

Agile Development ◽

Small Scale ◽

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

Cloud Computing Applications and Techniques for E-Commerce - Advances in Systems Analysis, Software Engineering, and High Performance Computing ◽

Cloud Enhances Agile Software Development

10.4018/978-1-7998-1294-4.ch002 ◽

2020 ◽

pp. 28-49

Author(s):

Saikat Gochhait ◽

Shariq Aziz Butt ◽

Tauseef Jamal ◽

Arshad Ali

Keyword(s):

Cloud Computing ◽

Software Development ◽

Process Model ◽

Security Measures ◽

Software Products ◽

Agile Methodology ◽

Software Product ◽

Agile Software ◽

Efficient Software

The software industries follow some patterns (i.e., process model to develop any software product). Agile methodology is the most famous and used process model. It is a trend to develop efficient software products with high client satisfaction. In this chapter, the authors discuss agile methodology and its components, benefits, and drawbacks while using the cloud computing in agile software development, existing frameworks for agile-cloud combination, and some security measures.

Cloud Enhances Agile Software Development

10.4018/978-1-6684-3702-5.ch025 ◽

2022 ◽

pp. 491-507

Author(s):

Saikat Gochhait ◽

Shariq Aziz Butt ◽

Tauseef Jamal ◽

Arshad Ali

Keyword(s):

Cloud Computing ◽

Software Development ◽

Process Model ◽

Security Measures ◽

Software Products ◽

Agile Methodology ◽

Software Product ◽

Agile Software ◽

Efficient Software

Towards Adopting Software Quality Assurance in Agile Development Methodology

Turkish Journal of Computer and Mathematics Education (TURCOMAT) ◽

10.17762/turcomat.v12i3.1158 ◽

2021 ◽

Vol 12 (3) ◽

pp. 2152-2157

Author(s):

Rosnani Shuib Et.al

Keyword(s):

Quality Assurance ◽

Software Development ◽

Agile Development ◽

Agile Methodology ◽

Agile Methodologies ◽

Development Methodology ◽

Quality Assurance Mechanism ◽

Software Product ◽

In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.

AGILE SOFTWARE DEVELOPMENT

International Journal of Engineering Applied Sciences and Technology ◽

10.33564/ijeast.2021.v05i12.011 ◽

2021 ◽

Vol 5 (12) ◽

Author(s):

Gopalkrishna Waja ◽

Jill Shah ◽

Pankti Nanavati

Keyword(s):

Software Development ◽

Extreme Programming ◽

Software Project ◽

Research Papers ◽

Agile Methodology ◽

Development Methodology ◽

Software Development Methodology ◽

Agile Software ◽

The Impact

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.

New Approach on the Agile Cycles Containment Effectiveness Metrics in Automotive SW Development

ACTA IMEKO ◽

10.21014/acta_imeko.v7i4.564 ◽

2019 ◽

Vol 7 (4) ◽

pp. 3

Author(s):

Ionut Andrei Sandu ◽

Alexandru Salceanu

Keyword(s):

Software Development ◽

Agile Development ◽

Extended Version ◽

New Approach ◽

Development Team ◽

Real Application ◽

Original Contribution ◽

<p class="Abstract"><span lang="EN-US">In an ideal Agile Development Team, defects should not exist. But in reality and especially in Automotive Agile Software Development, we need to have a mechanism for defects handling and tracking to closure. In this paper we describe the benefits and principles for measuring the defects handling metrics in automotive programs and organizations which adopted Agile SW Development. We are presenting the Iteration Containment Effectiveness, Program Increment Containment Effectiveness and Defect Debt Trend metrics. The acquired advantages are demonstrated by a detailed example of real application on how to measure the classical Phase Containment Effectiveness metric on Iteration (Sprint) and Program Increment (Scum of Scrums / Scaled Agile) Level. This paper is an extended version of the original contribution to the IMEKO TC 4 2017 symposium in Iasi, Romania.</span></p>

Achieving Enterprise Agility through Innovative Software Development - Advances in Systems Analysis, Software Engineering, and High Performance Computing ◽

Agile Enablers and Adoption Scenario in Industry Context

10.4018/978-1-4666-8510-9.ch008 ◽

2015 ◽

pp. 157-178

Author(s):

Vinay Kukreja ◽

Amitoj Singh

Keyword(s):

Software Development ◽

Agile Development ◽

User Requirements ◽

Distributed Environment ◽

Team Members ◽

Agile Methodologies ◽

Software Development Methodologies ◽

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Agile Software Development

Security-Aware Systems Applications and Software Development Methods ◽

10.4018/978-1-4666-1580-9.ch001 ◽

2012 ◽

pp. 1-15

Author(s):

Torstein Nicolaysen ◽

Richard Sassoon ◽

Maria B. Line ◽

Martin Gilje Jaatun

Keyword(s):

Software Development ◽

Agile Development ◽

Implementation Team ◽

Agile Methodologies ◽

Development Organizations ◽

Development Lifecycle ◽

Software Development Lifecycle ◽

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Agile Software Development Quality Assurance

Software Applications ◽

10.4018/978-1-60566-060-8.ch156 ◽

2009 ◽

pp. 2680-2699

Author(s):

James F. Kile ◽

Maheshwar R. Inampudi

Keyword(s):

Software Development ◽

High Performance ◽

General Rule ◽

Adaptive Methods ◽

Agile Development ◽

Performance Requirements ◽

Small Project ◽

Software Development Methodologies ◽

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

IMPLEMENTATION OF REUSE IN THE AGILE SOFTWARE DEVELOPMENT PROCESS SCRUM

Asian Journal of Pharmaceutical and Clinical Research ◽

10.22159/ajpcr.2017.v10s1.19597 ◽

2017 ◽

Vol 10 (13) ◽

pp. 143 ◽

Cited By ~ 1

Author(s):

Jayasudha R ◽

Viswanathan V ◽

Shanthi P

Keyword(s):

Software Development ◽

Development Process ◽

Dynamic Change ◽

Agile Development ◽

Software Development Process ◽

Customer Requirements ◽

Waterfall Model ◽

Agile Software ◽

First Time

The concept of reuse is applied in one of the agile development methodologies called the scrum. Sprint is a single functionality and the result at the end of the sprint functionality is derived as the shippable or bugs. This paper makes an attempt to use the concept of reuse in the agile software development to meet the dynamic change of customer requirements in banks. A banking project is created using both waterfall model and scrum model, and the knowledge gained is stored in the ontology-based repository for the first time. Again, the same project is created for different vendors using the ontology-based repository. The result shows that maximum sprint is reused and all the knowledge gained is stored in the form of ontology. This ontology helps identify the shippable component of each sprint which is a small executable functionality. This leads to less cost and time to deliver the product. The main aim is to increase the availability of the reusable artifacts, which lead to increase the reusability of the developer. The experimental results show improvements in the performance of retrieving the components for the software development.