scholarly journals Towards Adopting Software Quality Assurance in Agile Development Methodology

2021 ◽  
Vol 12 (3) ◽  
pp. 2152-2157
Author(s):  
Rosnani Shuib Et.al
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
Development Methodology ◽  
Quality Assurance Mechanism ◽  
Software Product ◽  
Agile Software

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.

scholarly journals AGILE SOFTWARE DEVELOPMENT

2021 ◽  
Vol 5 (12) ◽  
Author(s):  
Gopalkrishna Waja ◽  
Jill Shah ◽  
Pankti Nanavati
Keyword(s):  
Software Development ◽  
Agile 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.

Agile Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

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

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

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.

Quality Assurance in Agile Software Development

2014 ◽  
pp. 155-176 ◽  
Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Best Practices ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Software Life Cycle ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Agile Software

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.

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

2019 ◽  
pp. 1-12
Author(s):  
Ali Sever
Keyword(s):  
Cloud Computing ◽  
Software Development ◽  
Rapid Development ◽  
Agile Software Development ◽  
Distributed Teams ◽  
Agile Development ◽  
Computing Platform ◽  
Agile Methodology ◽  
Technological Advances ◽  
Agile Software

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.

Cloud Enhances Agile Software Development

2020 ◽  
pp. 28-49
Author(s):  
Saikat Gochhait ◽  
Shariq Aziz Butt ◽  
Tauseef Jamal ◽  
Arshad Ali
Keyword(s):  
Cloud Computing ◽  
Software Development ◽  
Process Model ◽  
Agile Software Development ◽  
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

2022 ◽  
pp. 491-507
Author(s):  
Saikat Gochhait ◽  
Shariq Aziz Butt ◽  
Tauseef Jamal ◽  
Arshad Ali
Keyword(s):  
Cloud Computing ◽  
Software Development ◽  
Process Model ◽  
Agile Software Development ◽  
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.

Agile Methodology of Development and How to be Compliant

2015 ◽  
pp. 268-283
Author(s):  
Yerramalli Subramaniam ◽  
Avik Pal ◽  
Arindam Dey
Keyword(s):  
Process Control ◽  
Software Development ◽  
Development Process ◽  
Life Science ◽  
Agile Software Development ◽  
Software Development Process ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
Product And Process ◽  
Agile Software

Given that Agile software development is preferred methodology for products and services in life science industry, in this chapter we will describe how to adopt Agile software development process and still be compliant. We will focus on few Agile methodologies and provide details on what design controls we can adopt in order for the product and process to be compliant. We will also focus on some of the tools that can be used to help put such design and process control in place where we can have complete transparency and traceability.

Quality Assurance in Agile Software Development

2018 ◽  
pp. 837-859
Author(s):  
Iwona Dubielewicz ◽  
Bogumiła Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Best Practices ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Software Life Cycle ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Agile Software

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.

Agile Methodology Adoption

2011 ◽  
pp. 118-123
Author(s):  
John McAvoy ◽  
David Sammon
Keyword(s):  
Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Initiation Phase ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
Development Methodology ◽  
Software Development Methodologies ◽  
Agile Software ◽  
Universal Solutions

Discussions on agile software development methodologies have a tendency to develop into an argument between proponents of agile methods and proponents of more traditional process-oriented methodologies. The terminology used in these debates is often unhelpful, and in many cases are inaccurate and biased representations. It needs to be accepted that there are no “silver bullets” providing universal solutions (Jeffries, 2001). Bearing this in mind, the decision to adopt a particular software development methodology is a difficult one, and the decision to choose an agile method is no exception. In theory, as in practice, definitions and descriptions of the various agile methods are presented, yet the factors considered in the decision to adopt, or not adopt, an agile method are not addressed. While agile methodologies try to avoid the excessive use of procedures or tools (Beck & Fowler, 2001), one agile methodology, dynamic systems development method (DSDM), does recommend the use of appropriate tools during the development process (Coesmans, 2003). However, it appears that none of the available agile methodologies suggest a tool to assist decision makers at the project initiation phase, therefore, the debate on agile suitability is usually a debate on agile versus traditional methods (DeMarco & Boehm, 2002), rather than an examination of the suitability of agile methods for a particular project. While the “agile debate” rages, individual projects are not adequately assessed prior to the adoption of a method.

Sign in / Sign up

Export Citation Format

Share Document