Search 250 million research papers

Agile Software Development

Christoph Schmidt · Progress in IS · 2015

Cited by 21

Agile Software Development

Torstein Nicolaysen, Richard Sassoon, Maria B. Line et al. · IGI Global eBooks · 2012

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.

Cited by 5

Agile Software Development

Hooda, Sushella, Sood, Vandana Mohindur, Singh, Yashwant et al. · 2023

AGILE SOFTWARE DEVELOPMENT A unique title that introduces the whole range of agile software development processes from the fundamental concepts to the highest levels of applications such as requirement analysis, software testing, quality assurance, and risk management. Agile Software Development (ASD) has become a popular technology because its methods apply to any programming paradigm. It is important in the software development process because it emphasizes incremental delivery, team collaboration, continuous planning, and learning over delivering everything at once near the end. Agile has gained popularity as a result of its use of various frameworks, methods, and techniques to improve software quality. Scrum is a major agile framework that has been widely adopted by the software development community. Metaheuristic techniques have been used in the agile software development process to improve software quality and reliability. These techniques not only improve quality and reliability but also test cases, resulting in cost-effective and time-effective software. However, many significant research challenges must be addressed to put such ASD capabilities into practice. With the use of diverse techniques, guiding principles, artificial intelligence, soft computing, and machine learning, this book seeks to study theoretical and technological research findings on all facets of ASD. Also, it sheds light on the latest trends, challenges, and applications in the area of ASD. This book explores the theoretical as well as the technical research outcomes on all the aspects of Agile Software Development by using various methods, principles, artificial intelligence, soft computing, and machine learning. Audience The book is designed for computer scientists and software engineers both in research and industry. Graduate and postgraduate students will find the book accessible as well.

Cited by 19

Agile Software Development

Challa Kaushik Koundinya · African Journal of Biomedical Research · 2024

The ever-evolving landscape of the software industry demands adaptable methodologies that align with its dynamic nature. Incremental Development, a revolutionary approach, emphasizes continuous reassessment and adaptation of plans, breaking down tasks into shorter iterations for enhanced efficiency. This paper explores the pivotal aspects of Agile Software Engineering through a comprehensive review of existing research. Additionally, it compares Contrasting Agile Methodologies to provide a nuanced understanding of their differences and advantages in contemporary software development environments.

Cited by 0Open access

Agile Software Development

James Noble · 2010

Cited by 69

Agile Software Development

Laurie Williams, Mladen A. Vouk · Wiley Encyclopedia of Computer Science and Engineering · 2007

Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan. Some examples of plandriven methods are various waterfall approaches and others such as the Personal Software Process (PSP) (2, 3) and the Rational Unified Process (RUP) (4, 5). An underlying assumption in plan-driven processes is that the requirements are relatively stable. On the other hand, iterative methods, such as spiral model-based approaches (6, 7), evolutionary processes described in Refs. (8, 11), and recently agile approaches (12) count on change and recognize that the only constant is change. The question is only of the degree and the impact of the change. Beginning in the mid-1990s, practitioners began finding the rate of change in software requirements increasing well beyond the capabilities of classic development methodologies (1, 13). The software industry, software technology, and customer expectations were moving very quickly, and customers were becoming increasingly less able to fully state their needs up front. As a result, agile methodologies and practices emerged as an explicit attempt to more formally embrace higher rates of requirements change. In this chapter, we provide background information on agile principles and an overview of three agile methodologies.

Cited by 1

Agile Software Development

Muga Nishizawa, Dissertation Chair, Shigeru Chiba · 2008

This thesis proposes two new language constructs for aspect-oriented programming (AOP) and a new AOP language that provides those language constructs. AOP is useful for agile software development. However, existing AOP languages have not been used on agile software development yet. This is because existing AOP languages are not good enough for agile software development. This thesis first analizes the features of agile software development and shows that AOP is useful for agile software development with two example scenarios. Then it explains that AspectJ is not good enough for concurrent development by several software engineers and for developing distributed software in the agile methods. AspectJ is one of existing general-purpose AOP languages for Java. To solve the problems of existing AOP languages such as AspectJ, this thesis presents our AOP language named GluonJ. GluonJ is based on AspectJ. It provides mechanisms for pointcut-advice and inter-type

Cited by 0

Agile software development

Dingsoyr, Torgeir, Dyba, Tore, Moe, Nils Brede · CERN Bulletin · 2010

Cited by 0

Agile Software Development

Torstein Nicolaysen, Richard Sassoon, Maria B. Line et al. · International Journal of Secure Software Engineering · 2010

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.

Cited by 49

Agile Software Development

Stewart, Rhonda · Nottingham ePrints (University of Nottingham) · 2009

One of the most noticeable changes to software process thinking in the last ten years has been the appearance of the word ‘agile’ (Fowler, 2005). In the Information Technology (IT) industry Agile Software Development, or simply Agile is used to refer to a family of lightweight development approaches that share a common set of values and principles1 focused around adapting to change and putting people first (Fowler, 2005). Such Agile methods2 provide an alternative to the well-established Waterfall model for software development (Royce, 1970). Traditionalists, those in favour of plan-driven approaches such as Waterfall see Agile as a threat to the Software Engineering profession, sparking on-going debate (Ambler, 2001)(Davis, 2004).\nAgile has benefited from the controversy it has ignited, as well as the considerable marketing hype of the last few years. This report seeks to go beyond the build-up to explore Agile in more depth and identify the current state of this emergent practice. Agile ideas are traced through Industrial and Software Engineering history to illustrate their early influences as well as the gradual growth of these concepts into what we now recognize as Agile. The reader is introduced to Agile philosophy and four of its leading methods. As Agile’s effects are now reaching beyond software development and into the Project Management space, Agile Project Management is compared and contrasted with the traditional project management framework. Lastly, key advantages and disadvantages of Agile Software Development are provided.

Cited by 0

Agile Software Development

Peter Wlodarczak · Auerbach Publications eBooks · 2023

Agile Software Development is an introduction to agile software development methods. Agile methods try to diminish complexity, increase transparency, and reach a deployable product in a shorter time frame. Agile methods use an iterative and incremental approach to minimize risks and to avoid maldevelopment. The book gives a short introduction to agile methods and agile software development principles. It serves as a study book and as a reference manual. Based on the official Scrum Guide, the book also covers other topics such as best practices for agile software development and agile testing. It targets practitioners who want to start with agile software development, as well as developers or project managers who already use agile methodologies. The book can be read from the beginning, but each chapter has been written in a way so it can be read individually.

Cited by 2

Agile Software Development

Olga Seredinskaya, L.I. Meshcheryakov, T.I. Morozova · Institutional Repository National Mining University of Ukraine (National Mining University of Ukraine) · 2017

Cited by 0

Software Engineering: Agile Software Development

Anubhavi Rastogi, Sachin Jain · International Journal of Advanced Research in Science Communication and Technology · 2023

Research examines the advantages and difficulties of using agile software development approaches. An overview of the literature on agile software development is presented first, followed by an introduction to agile approaches and their characteristics. The case study strategy used in this study's research methodology combines qualitative and quantitative data collection methods. In order to assess the project's success factors, team productivity, and customer satisfaction, the case study focused on a software development project that used agile methodology. The results of this study show that agile techniques have many advantages for software development projects, including improved client satisfaction, better cooperation, and flexibility. The use of agile approaches, however, is not without its difficulties. Agile software development has grown in popularity in recent years, especially in the software industry, where it is considered to boost productivity, decrease risk, and improve customer satisfaction. Other disciplines, including as project management, product development, and marketing, have also adopted the agile methodology. While agile software development has numerous advantages, it also has some drawbacks, such as managing stakeholder expectations, guaranteeing team participation, and preserving quality.

Cited by 1Open access

What Makes Agile Software Development Agile?

Marco Kuhrmann, Paolo Tell, Regina Hebig et al. · IEEE Transactions on Software Engineering · 2021

Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders’ collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15 percent). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

Cited by 83Open access

Contextualizing agile software development

Philippe Kruchten · Journal of Software Evolution and Process · 2011

SUMMARY This paper presents a contextual model for software‐intensive systems development to guide the adoption and adaptation of agile software development practices. This model was found especially useful when the project context departs significantly from the “agile sweet spot”, that is, the ideal conditions in which agile software development practices originated from, and where they are most likely to succeed, “out of the box”. This is the case for large systems, distributed development environment, safety‐critical systems, system requiring a novel architecture, or systems with an unorthodox business model or governance model. Copyright © 2011 John Wiley & Sons, Ltd.

Cited by 152

Agile Software Development Methods

Firas Glaiel, Allen Moulton, Stuart Madnick et al. · 2013

Abstract — While Agile software development has many advocates, acceptance in the government and defense sectors has been limited. To address questions of meanings to the term “Agile, ” we examine a range of Agile methods practiced and develop a framework of seven characteristics, which we call the Agile Genome. We gain insight into the dynamics of how Agile development compares to classic “waterfall ” approaches by constructing a System Dynamics model for software projects. The Agile Project Dynamics (APD) model captures each of the Agile genes as a separate component of the model and allows experimentation with combinations of practices and management policies. Experimentation with the APD model is used to explore how different genes work in combination with one another to produce both positive and negative effects. The extensible design of the APD model provides the basis for further study of Agile methods and management practices. 1.

Cited by 0

Agile Global Software Development

Rafael Camara, Annelyelthon Alves, Iury Monte et al. · 2020

Global Software Development (GSD) continues to grow substantially and it is fast becoming the norm and fundamentally different from local Software Engineering development. Withal, agile software development (ASD) has become an appealing choice for companies attempting to improve their performance although its methods were originally designed for small and individual teams. The current literature does not provide a cohesive picture of how the agile practices are taken into account in the distributed nature of software development: how to do it, who, and what works in practice. This study aims to highlight how ASD practices are applied in the context of GSD in order to develop a set of techniques that can be relevant in both research and practice. To answer the research question, "how are agile practices adopted in agile global software development teams?" We conducted a systematic literature review of the ASD and GSD literature. A synthesis of solutions found in seventy-six studies provided 48 distinct practices that organizations can implement, including "collaboration among teams", "agile architecture", "coaching", "system demo" and "test automation". These implementable practices go some way towards providing solutions to manage GSD teams, and thus to embrace agility.

Cited by 17

Agile software development management

Turach, D. V. · Репозиторий БГУИР (BSUIR Repository) · 2016

Computer science is a young science. Computer programmers my age were trained by engineers. That training dictated 
\nhow we approached software development for an entire generation. But now after decades of building software to be expensive, 
\nunwanted, and unreliable we have come to realize software is different. Building software is more like creating a work of art, it 
\nrequires creativity in design and ample craftsmanship to complete. Software remains malleable, often illogical, and incomplete 
\nforever. Agile software development is based on fundamental changes to what we considered essential to software development 
\nten years ago.

Cited by 0

AGILE SOFTWARE DEVELOPMENT METHODS

SIDOROVA, ALYONA, MOSHTAGH, YEVHENIIA S. · A.N.Beketov KNUME Digital Repository (National University of Kharkiv) · 2018

Cited by 0Open access

Software Development Agile Methods

Dreiseitel, Jiří · Brno University of Technology Digital Library (Brno University of Technology) · 2015

Práce popisuje základní principy agilního vývoje software a uvádí jejich výhody oproti tradičnímu přístupu. Kombinaci agilních metodik Scrum a Kanban používá společnost Siemens v Brně v rámci organizačních procesů, proto se práce zaměřuje především na metodu Scrum, Kanban, Scrum-ban a porovnání těchto metod mezi sebou. Práce se dále zabývá analýzou existujícího projektu, výsledek této analýzy byl předložen konzultantovi ve společnosti Siemens společně s návrhy na zlepšení. Po vzájemné domluvě byl navržen a implementován zásuvný modul pro systém JIRA. Tento modul rozšiřuje současné možnosti analýzy existujících projektů z pohledu agilních metodik, což vede k podpoře při rozhodování v rámci agilních procesů. Závěrem práce je diskutován přínos implementovaných řešení a možné směry dalšího rozvoje.

Cited by 0