Agile Methodology: A new Approach over Traditional Methodology

Software development methodology consists of dividing the software development process or work into different phases in order to achieve better planning and management. As the software development proceeds, factors such as requirements, needs, priorities, underlying technology may change. Thus development process must be highly dynamic and a good software development methodology must adapt to these evolving and changing requirements. Traditional software development models are unable to handle such dynamic requirements. To cope up with such dynamic requirements a set of software development methodologies referred as " Agile Software development methodologies " are used. Comparison between different Agile software development methods will help in the selection of appropriate development model given a particular scenario.

2007

Product or company names used in this set are for identification purposes only. Inclusion of the names of the products or companies does not indicate a claim of ownership by IGI of the trademark or registered trademark.

International Journal of Information Technologies and Systems Approach, 2020

Agile practices are activities or procedures that are applied during the software development process in order to improve its quality and productivity. The objective of this study is to determine the influence of agile practices on software quality. For this purpose, a model composed of 4 groups of agile practices and 8 quality characteristics according to the ISO/IEC 25010 standard has here been proposed. The results of 146 questionnaires addressed to people involved in the software development process show that the application of agile engineering and project management practices have a significant positive influence on the quality attribute functionality. On the other hand, project management practices have a low impact on the quality characteristics of compatibility, portability, security, and usability.

International Journal of Advanced Computer Science and Applications, 2019

The software industry used software development lifecycle (SDLC) to design, develop, produce high quality, reliable and cost-effective software products. To develop an application, project team used some methodology which may include artifacts and pre-defining specific deliverables. There are different SDLC process models such as waterfall, iterative, spiral and agile model available to develop a quality product. In this paper we focus only on agile software development model, and Scrum model and their techniques. There are many papers and books written on agile methodologies. We will also use their knowledge in this paper. To collect data for comparison of agile method with software quality affecting factors, an online questionnaire survey was conducted. The survey sample consisted of software developers with several years of industry experience using agile methodologies. The main purpose of this study is to compare software quality affecting factors with agile and scrum model.

2006

This research paper discusses the software development through agile approaches. In which we see that most of the time, agile approaches cannot use for all type of projects. But this paper is exploring the new ideas that how we can use the agile methodologies with the help of traditional approach and PSP/TSP/Software CMMI. So, the over all paper is giving the whole idea, that we can develop any type of software projects through the new agile methodology guidelines which we are describing here. As well as for solving this paper we adopted different ways in which we focused on literature study & also published research paper on agile methodology. In addition, we did this work on the base of hybrid ideology where we combined the best ways of different approaches and achieved our goals.. Where we proved that by the combination of these approaches, we can manage our projects as well as team personals in the organization successfully. And this concept for team management comes from PSP/TSP and Software CMMI. The benefit for management of this is also to get our projects with agility and personnel's training for project management.

This paper is a review research about the features of the agile and heavy (traditional) software development methodologies and comparisons between them based on: Investment and Team Size. The important difference between agile and heavy methodologies is the adaptability for project changes. In agile methodologies changes do easily but heavy methodologies are static and do not adapt with changes. Also in this paper there are the usage of each groups of methodologies and how can work two groups together. In addition, some types of heavy and agile methodologies have been described.

… of the 20th international conference on Software …, 1998

This article proposes a new software process model, ASP (Agile Software Process) and discusses its experience in a large-scale software development. The Japanese software factory was a successful model in the development of quality software for large-...

2021

The goal of every project/software manager is to deliver an efficient product at the end of the development cycle that comfort with user requirements as stated at the beginning of the planning stage. To achieve this goal, requires choosing a technique or methodology that will help to achieve such results, easily, timely, and with less budget while ensuring product result quality. Traditional methodologies such as Waterfall, spiral and others, are the well-known software and project management methods in use. However, due to advancement in technology, scalability and complexity of projects, there is need for the use contemporary and advanced techniques that will conform with the ever growing world of technological advancement. It is in line with the aforementioned development, developers and managers used agile methods often for software development and project management. This research is aim at making a critical analysis on the factors that makes the agile methods used most in comparison to traditional methods (such as waterfall).

Journal of Software Engineering & Intelligent Systems, 2020

Quality assurance is one of the important issues for software companies because the delivery of high-quality software for customer satisfaction is much needed. Software quality is a relatively complex concept, but many companies have standards for quality assurance. In agile methods, developers are responsible for quality assurance. Agile methods involve many practices for quality assurance. Moreover, quality assurance in the waterfall model in each stage by using different practices is done for validation. Quality assurance has many parameters, to control software quality, that are also discussed. The traditional quality assurance is carried out periodically at various stages, but the agile quality assurance is constantly being carried out by the team on daily basis. In this paper, we mentioned ways to improve quality assurance in agile development.

Advances in Systems Analysis, Software Engineering, and High Performance Computing, 2014

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.