Agile Software

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.

Agile Methodology Adoption

Encyclopedia of Information Science and Technology, Second Edition ◽

10.4018/978-1-60566-026-4.ch021 ◽

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.

Extending Security in Agile Software Development Methods

Integrating Security and Software Engineering ◽

10.4018/978-1-59904-147-6.ch007 ◽

2007 ◽

pp. 143-159 ◽

Cited By ~ 1

Author(s):

M. Siponen ◽

R. Baskerville ◽

R. Kuivalainen

Keyword(s):

Information Systems ◽

Software Development ◽

Agile Methods ◽

Agile Method ◽

Management Standards ◽

Secure Information ◽

Agile Software ◽

Development Methods ◽

Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

Information Security and Ethics ◽

10.4018/978-1-59904-937-3.ch059 ◽

2008 ◽

pp. 845-858

Author(s):

M. Siponen ◽

R. Baskerville ◽

T. Kuivalainen

Keyword(s):

Information Systems ◽

Software Development ◽

Agile Methods ◽

Agile Method ◽

Management Standards ◽

Secure Information ◽

Agile Software ◽

Development Methods ◽

Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Management of software development projects in Brazil using agile methods

Independent Journal of Management & Production ◽

10.14807/ijmp.v12i5.1353 ◽

2021 ◽

Vol 12 (5) ◽

pp. 1357-1374

Author(s):

Claudia Carrijo Ravaglia ◽

Mirian Picinini Mexas ◽

Ana Claudia Dias ◽

Haydée Maria Correia da Silveira Batista ◽

Kleber da Silva Nunes

Keyword(s):

Software Development ◽

Management Practices ◽

Field Research ◽

Distributed Teams ◽

Agile Methods ◽

Management Decision ◽

Development Projects ◽

Agile Methodology ◽

Management Decision Making ◽

The aim of the paper is to analyze how agile management practices are being adopted by specialists from software development technology companies in Brazil, identifying actions that contribute to the success of software implementation, aiming to ensure the survival of organizations in the market. The study counted with a literature review to support the field research with software development specialists who use the agile methodology and work in Brazil in the states of Rio de Janeiro and São Paulo. The results were analyzed through a descriptive statistics and content analysis. The research identified that the companies that adopt agile software management methodology in Brazil prefer the Scrum method and the development teams may be geographically distributed. The main positive points identified when adopting agile methods were the process speed, team involvement, maximization of results, involvement with the client, and simplicity. Most experts identified problems in the implementation of the agile methodology and as points of attention: management of distributed teams, scope estimation and communication. It was possible to identify the existence of a positive financial result by adopting the agile method for software development projects, as well as actions that contribute to the success of these projects, such as controlling quality using different testing techniques, project management, time, stakeholders, scope, and have agile communication, with feedback and good leadership. On the other hand, it was observed in the statistics that, although efficient, this method is still not being widely used. This research can contribute to the managers of software development companies in the use of agile methods as well as improving management decision-making.

An Analysis of Process Characteristics for Developing Scientific Software

Journal of Organizational and End User Computing ◽

10.4018/joeuc.2011100105 ◽

2011 ◽

Vol 23 (4) ◽

pp. 64-79 ◽

Cited By ~ 5

Author(s):

Diane Kelly

Keyword(s):

Software Engineering ◽

Software Development ◽

Professional Training ◽

Scientific Software ◽

Development Environment ◽

Engineering Development ◽

Development Processes ◽

Agile Software ◽

Development Methods ◽

Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

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.

Exploring the Role of Project Management in the Development of the Academic Agile Software Discourse: A Bibliometric Analysis

Project Management Journal ◽

10.1177/875697281704800101 ◽

2017 ◽

Vol 48 (1) ◽

pp. 3-18 ◽

Cited By ~ 6

Author(s):

Thomas G. Lechler ◽

Siwen Yang

Keyword(s):

Project Management ◽

Software Development ◽

Bibliometric Analysis ◽

Agile Methods ◽

Management Research ◽

Practical Applications ◽

Time Period ◽

Time Periods ◽

The practical applications of agile methods and their impact on the productivity and efficiency of software development dominate the agile literature. We analyzed 827 academic articles with bibliometric techniques to explore the role project management research played in the development of the academic agile discourse. Bibliometric analyses over two time periods reveal that project management–related topics form a distinct stream of research in the second time period but not in the first. Furthermore, our results reveal that the academic agile discussion has been mainly unidirectional. This situation offers many opportunities for project management researchers to contribute to the agile discourse.

Handbook of Research on Information Architecture and Management in Modern Organizations - Advances in Information Quality and Management ◽

Using Wiki for Managing Knowledge in Agile Software Development

10.4018/978-1-4666-8637-3.ch018 ◽

2016 ◽

pp. 397-423

Author(s):

Pankaj Kamthan

Keyword(s):

Software Engineering ◽

Software Development ◽

Software System ◽

Web Environment ◽

The Past ◽

Agile Methodologies ◽

The Social ◽

Industrial Software ◽

The movement towards agility is one of the most significant changes in industrial software engineering over the past decade. In the practice of agile methodologies, there are different types of knowledge that is created, communicated, and consumed. For the benefit of the stakeholders involved, there is a pressing need to manage this knowledge, both during development and beyond deployment of a software system. This chapter proposes a framework comprising related conceptual models as means for understanding the use of Wiki for managing knowledge in agile software development. In doing so, Wiki is considered beyond that of a technology or a tool, as a facilitator of knowledge, and placed in a larger context of the Social Web environment. For the sake of practicality, a number of illustrative examples are given, and implications of deploying a Wiki are highlighted.

Advances in Systems Analysis, Software Engineering, and High Performance Computing - Balancing Agile and Disciplined Engineering and Management Approaches for IT Services and Software Products ◽

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

10.4018/978-1-7998-4165-4.ch011 ◽

2021 ◽

pp. 205-227

Author(s):

Michal Dolezel ◽

Alena Buchalcevova

Keyword(s):

Software Development ◽

Classification Scheme ◽

Organizational Structures ◽

Agile Methods ◽

Two Dimensional ◽

Dimensional Classification ◽

Agile Software ◽

Structural Mechanisms ◽

Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.