Figure - uploaded by Gaurav Kumar
Content may be subject to copyright.
Figure1: Agile Software Development Methodologies with Benefits
Source publication
Abstract – Agile methodology that utilizes iterative development and prototyping are widely used in variety of industry projects as a light weight development method which can satisfy to the changes of requirements. Short iterations are used that are required for efficient product delivery. Traditional software development processes are not much ef...
Similar publications
The combination of Agile methods and distributed software development via remote teams represents an emerging approach to address the challenges such as late feedback, slow project timelines, and high cost, typically associated with software development projects. However, when projects are implemented using an Agile model with distributed human res...
Agile methodologies are being used all through the lifecycle of the software development, not simply the development phase, and regularly in complex situations that require high than the small and collocated team. In the present turbulent markets, where organizations are irately fighting from new businesses and additional rebellious opponent, the p...
Today, organizations tailor the practices from several agile methodologies to serve their particular environment. But are there situations that drive how an organization should tailor methodologies in a particular manner? This article places 12 commonly used agile development practices into a typology based upon whether they are primarily project m...
Software estimation models focuses on estimate the size, time, and cost required to complete the project. The Agile methodologies are more different compared with traditional methods. Thus by the use of traditional effort estimation models can be lead to inaccurate effort estimation. This paper aims to improve the effort estimation accuracy in soft...
Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and ef...
Citations
... Most of the organizations now finding the benefits of agile and moving towards it but caution is required [Strode et al. (2009)]. As lot of IT projects now being developed in agile than mission critical systems paving way for agile [Malik et al. (2019) and Kumar et al. (2012)]. However, I recommend in this paper a balanced approach need to be adapted with fine blend of both models based on phase wise with benefits of optimal cost and speed. ...
... Its principles and values continue to shape the way projects are managed, promoting agility, continuous improvement, and adaptability (Kumar and Bhatia, 2012). ...
The purpose of conducting this research is to explore how Artificial Intelligence (AI) might augment the profession of project management, especially in the context of Agile project management.
This study is motivated by the burgeoning presence of AI as a game-changer technology that warrants a compelling investigation into its implications on the future of Agile methodologies.
During this research, a total of 5 project management experts with extensive backgrounds in Agile project management and IT/software development were asked to share their vision for the future of Agile project management in an era where AI has been taking organizations and industries by the storm.
The results obtained from the interviews conducted would seem to suggest that the advent of AI could lead to certain modifications and ramifications in Agile practices and dynamics within scrum teams. While certain roles might be subject to automation in the next decade, the extent of these changes varies considerably.
What is certain is that a lot of Agile tools could benefit from the incorporation of AI integration, as it has been proven to significantly minimize the occurrence of human errors and maximize efficiency. This optimization enables scrum teams to divert their efforts from mundane tasks to areas where the human touch adds substantial value to projects.
However, with great efficiency comes great responsibility, and careful ethical considerations must be taken to prevent the overreliance on Artificial Intelligence. The efficiency of automation, while promising, carries inherent disruptive potential, particularly with its implications for society, the environment, and job markets.
Nevertheless, the future of AI integration within project management holds promise, envisioning a landscape where certain roles transform while novel opportunities emerge.
In the face of these multidisciplinary challenges, project managers, product owners, scrum masters, designers, developers, and QAspecialists must adapt to the evolving landscape. Through a sustainable project management paradigm, these professionals can navigate the complexities of AI integration while harnessing its transformative potential.
Collaboration with AI-powered tools liberates crucial time, enabling teams to focus on intricate problem-solving, strategic decision-making, and higher-order creative thinking.
This dissertation provides an exhaustive exploration of sustainable project management within the AI era, investigating its potential impacts on Agile team dynamics, job roles, and project practices. Employing meticulous analysis, real-world cases, and empirical research, this study aspires to offer actionable insights and strategies to Agile practitioners, enabling them to embrace the possibilities of AI while safeguarding their crucial roles in shaping the trajectory of project management's future.
Furthermore, considering the ongoing evolution of Agile and its potential for breakthroughs, the exploration also contemplates the possibility of an “Agile renaissance”, suggesting that the full extent of AI's transformative power on Agile methodologies might still be on the horizon.
... This will help us to understand the required assistance to model the migration process of the legacy systems using the Agile methods. Agile software development approaches are incremental in nature to ensure customer satisfaction by rapid, continuous delivery of useful software [10]. In Agile practice, the deliverables are broken up into several iterations or Sprints of the same duration (typically between 2 to 4 weeks). ...
Many organizations rely on legacy applications for critical business pro- cesses, even though it incurs a huge cost due to obsolete hardware, software, compiler and the like. Replacing the business critical legacy requires extensive expertise to understand business requirements, esti- mate and test coupled with high cost. To ensure a strict cost budget of legacy migration projects, migration specialists need assistance to understand the facts of the legacy application component in a short span of time to estimate and deliver the target components. Avail- able program assistance tools do not address the needs to migrate the legacy applications. We have designed an effective framework to extract the run-time behaviour of the legacy application like function point, complexity, memory accesses and the like so as to estimate the scope and requirements of an application. The framework contains support to comprehend existing legacy applications, develop and test the target application with business-rules, non-functional requirements (NFR), test data, etc. Then we have proposed a tool assisted Agile way-of-working principles by augmenting our tool-set to migrate the legacy application quickly and effciently. The target components can also be validated co- existentially by exchanging live data with the existing legacy. Designed toolset is built on an open-source dynamic instrumentation framework and can be plugged to a wide variety of run-time environments.
... More in details, the Agile software development should start with simple and predictable approximations to the final requirement and then continue to increase the detail of these requirements throughout the project life cycle. This incremental refinement continuously improve the design, coding and testing at all stages of production activity [10]. Following the agile methodology two iterations were done, in which a series of interviews and webinars with judicial actors are carried out. ...
The digital transformation of public administrations (PA) plays a central role in the social and economic growth of a country. Currently, the application of Information Technology in government services, namely e-government, is still in its infancy and many applications are new born. The use of Artificial Intelligence (AI) could help improve the digital transformation of the PA. Although AI is a hot topic that is already used in everyday life and is constantly evolving, when it comes to the public sector, and in particular the justice sector, it is always difficult to think and recognise AI applications that actually help citizens and society. The main goal of this paper is to explore AI applications in the public domain to show how a real application in the justice sector could be helpful. Then, some results of real applications in the Court of Appeal of Naples are discussed and some future directions are proposed.KeywordsE-GovernmentPublic AdministrationArtificial Intelligence
... While other software development approaches use planning as a control mechanism, the agile methodology uses feedback [9]. Agile techniques have been shown to improve the quality of the software development process since it is more people than process-oriented [10]. The success of this methodology relied heavily on feedback from users, regular tests and evolution of different versions. ...
... Agile software development refers to the development of technological methods and software with the help of a diverse group of workforces and cross-functional teams (Kumar & Bhatia, 2012), in short periods. Thus, we emphasize the importance of self-directed teams that help facilitate collaboration and technological adaptation. ...
Surviving in a digitally disrupted world required organizations to continuously innovate and digitally transform their work practices, especially HR processes. Scholarly failure to define and conceptualize the construct of human resource digital transformation (HRDT) suggests the lack of an integrated approach to understanding HRDT as a discipline. This study presents an overarching and integrated conceptual framework of HRDT, grounded in robust qualitative research, to describe factors in successfully implementing HRDT. Drawing insights from 20 senior HR professionals in multinational organizations, this study defines HRDT as a multidimensional construct resulting from successful integration of digital and individual factors into the innovation capability of organizations. Expanding the dynamic-capabilities perspective, this study proposes that in uncertain and turbulent times, such as COVID-19, businesses must constantly upgrade organizational capabilities, manifested in the innovation capability with enablers such as-digital infrastructure, architecture, and individual capability and creativity. This research further elaborates on HRDT indicators.
... (Beam et. al., 1987;Ahmed et al., 2010;Kumar & Bhatia, 2012;Oliveira et al., 2018) also several researchers have stated that Feature-driven Development (FDD), code reusability, and design patterns will also lead to delivery excellence for the software development process as they would optimise the actual efforts for designing and coding. (Budoya et al., 2019;AlOmar et al., 2020;Mor et al., 2015) H5: There is a significant impact of Agile software engineering practices on delivery excellence function. ...
Purpose: This study explores the effect of the adoption of AI tools and frameworks on the productivity of Agile software development teams with high attrition rates. Design/methodology/approach: For this study, uses a combined theory approach to build and test a model for the effects of productivity factors along with the impact of AI technology on to the Agile software development team's productivity having a high attrition rate. A web-based survey is used to collect the sample data, which was eventually tested with the help of SmartPLS using partial least square methods and Bootstrapping. Findings: This study shows that the adoption of AI technology has a partial mediation effect on the Agile software development teams having a high attrition rate but could help sustain it by automating mundane tasks for predictable outputs. Research limitations/implications: Limited availability of data regarding factors of productivity, inadvertent sampling bias, and selecting the appropriate size of a data sample. Originality: The study findings shows that the AI technologies and tools, will help teams to sustain their productivity even though there are constraints like high attrition.
... Agile development methods such as Scrum or Kanban are extremely popular because of their flexibility and customer-centric approach. [13][14] These needs are usually inspired by human needs or business needs, the use/application of which supports a company's operations or gives it an advantage over its competitors. These needs can also be called the drivers of software development. ...
In the case of software development, we can talk about several methodologies, such as the waterfall model, test-driven software development, agile software development, but the question rightly arises whether software development methods in the traditional sense are applicable to the development of natural language processing language models, especially from the aspect of AI and dictionary-based NLP models. Learning AI models is substantially different from the classical software development process. Whereas in classical software development, developers explicitly describe the operation and behavior to the computer, in AI model learning, the models themselves learn from the input data. This paper presents a possible solution that applies the agile Scrum methodology used in classical software development to the development of dictionary-based NLP models, and identify the agile development opportunities in case of the machine learning-based NLP models.
... Then, at that point, to decrease utilization, Scrum is utilized, with the guide of highlight pushed improvement, dynamic improvement strategy, versatile programming program company utilized. As checked with the guide of utilizing A. Ahmed et al [7], the scrum is the greatest normally utilized, half of the drives are refined with the exuberant contribution of partners. 66.7% of respondents concur that usefulness has [7] have demonstrated that dexterous procedures are prominent for a couple of programming conditions, yet at this point no longer for all. ...
... As checked with the guide of utilizing A. Ahmed et al [7], the scrum is the greatest normally utilized, half of the drives are refined with the exuberant contribution of partners. 66.7% of respondents concur that usefulness has [7] have demonstrated that dexterous procedures are prominent for a couple of programming conditions, yet at this point no longer for all. With drives identified with huge groups, very much depicted prerequisites, unreasonable guarantee customers, and enormous code bases verifiably orientated endeavor profiles artistic creations well. ...
... Absence of side interest in design and construction inconveniences also. Behrouz Far planned programming unwavering quality designing into a light-footed improvement measure [7]. As indicated by the examination, test-pushed improvement does now at this point don't look all around coordinated with the dependability model. ...
A fast procedure that utilizes hopeless improvement and prototyping is by and large used in various business drives as a lightweight improvement methodology that can meet the necessities. Short practices use what you need for green thing development. The strategy for standard programming program improvement isn’t for every circumstance incomprehensible in managing the rapid substitute of necessities. Enhancements to the product improvement measure incorporate more steady necessities, prior flaw location, decreased testing times, expanded interoperability, and expanded versatility. Various approaches require various changes in programming advancement and the board culture. Various elements can, straightforwardly and in a roundabout way, influence improvement projects in the deft system. The reception of nimble improvement strategies decidedly affects both usefulness and quality. Thus, both the advancement group and the client are happy with its execution in programming improvement measures. Dismissing the advantages of perfection, the grievance of the speedy strategy isn’t consistently enchanted by both turn of events and plan, and no little coordinators can pass on little makers. Here, In this paper, we concentrate on a deft system to check the impact of the program improvement technique for quality, focal and social necessities.
... Agile methodology is a set of software development methods based on iteration and increment development, it uses iterative development that is widely used in a variety of industrial projects as a lightweight development method that can meet the changes of requirements. The four main characteristics that the fundamental principles of all agile methodologies are: Planning, iterative and scalable development, fast and flexible response to change, and improved communication [4,5]. ...
... Teamwork in agile processes works differently from the traditional software methodology such as waterfall methodology in which the team members work separately. Also, agile process involves developers, testers and business people to work together during all project stages [5]. ...
... Agile types have been used for every levels from developing traditional software to designing complex new integrated systems, they mainly depend on the process of incremental development [5]. In scrum method which is the most commonly used type of agile methods, the entire development cycle is divided into a series of iterations where each iteration is called as a sprint in every new iteration there are new functionalities that need to be added and combined with the functionalities of the system [12]. ...
In the field of software development, there are two areas constantly evolving during the software engineering process, which are software development methodologies and software architecture design patterns. It has become indispensable to shed light on them in terms of the suitable selection of developers to employ the appropriate types of them to obtain more efficiency of their work together, improving the quality of the software applications, and to produce software that has a high level of accuracy. The aim of this research is to determine and define the features that MVC architecture design pattern and agile methodology work by software engineering and development process, and to investigate how those features, that existing in both, could assist them to work in harmony without conflict in the way of work, and whether they support each other when they employ together on one software project. Also, how that compatibility will increase their ability to improve the quality of software products,. Two types of research methods have been used in this paper. Firstly, we used previous studies and experiences of researches to collect and determine the most important criteria that contribute to the success and excellence of software products, which are the advantages granted by the use of both Agile methodology and MVC architecture. The second method is distributing two questioners to participants that their experiences are up to 5 years, the first one is for the MVC framework and the other is for the Agile process, both of them are distributed to investigate the extent of the existence of these criteria from the point of view of experts who participated in answering these questionnaires. We used the results of both questionnaires and previous research to study how to obtain the advantages of using the two technologies, employing them, and applying them together to increase the efficiency of the resulting software product and that they support each other in practice.
