scholarly journals Adopting to Agile Software Development

2014 ◽  
Vol 16 (1) ◽  
pp. 64-70 ◽  
Author(s):  
Gusts Linkevics
Keyword(s):  
Expert System ◽  
Reference Material ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Complex Process ◽  
Agile Software

Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for a particular organization or a team. This research focuses on identification of agile methods and practices. Result of the research is the ranking of agile methods, practices and their usage trends. As some terms of agile software development are interpreted differently in different organizations and teams, terminology used is analyzed. Results of the research can be used as a reference material for those who are planning to adopt agile methods or are looking for the next agile practice to implement. Results will be used for the development of an expert system to support agile adoption.

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

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
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.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile 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

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile 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.

scholarly journals Applications supporting utilization of agile methods in software development process

2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Methods ◽  
Tabular Form ◽  
Software Development Process ◽  
Internet Applications ◽  
Technical Requirements ◽  
Development Processes ◽  
Agile Software

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

scholarly journals The Alignment of Business Strategy with Agile Software Development within SMEs

2010 ◽  
pp. 215-233 ◽  
Author(s):  
Pattama Kanavittaya ◽  
Jocelyn Armarego ◽  
Paula Goulding
Keyword(s):  
Software Development ◽  
Business Strategy ◽  
Business Performance ◽  
Agile Software Development ◽  
Agile Methods ◽  
It Strategy ◽  
Agile Methodologies ◽  
New Information ◽  
Multiple Case ◽  
Agile Software

The alignment of business strategy and IT strategy has been recognised as a strategic weapon within organisations. Small and medium sized enterprises (SMEs) also recognise a need for new Information Technology and Information Systems (IT/IS) functions to support business strategies, and provide new services to the market. Agile methodologies support the timely and economical development of Web and Internet-based software, the technologies being exploited by organisations seeking to enhance their business performance. Based on multiple-case research, this paper explores the impact of agile software development on the alignment of business strategy with IT strategy in SMEs. Several models of strategic alignment developed for large enterprises were used to examine the SME environment. The findings suggest that agile methods are applied to provide added flexibility for organisations to create or react to new opportunities, to increase responsiveness to customer requirements not possible with traditional software development, and to gain competitive advantage. Personal interest was found to be a factor in adopting agile methodologies, in addition to IT maturity and technical IT sophistication. However, the use of agile methods in response to internal and external uncertainty may change the role of ICT in the firms, and hence impact on the alignment of business and IT/IS strategy.

Security Assurance in Agile Software Development Methods

2022 ◽  
pp. 929-946
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Evaluation Framework ◽  
Agile Methods ◽  
Software Projects ◽  
Security Engineering ◽  
Security Incident ◽  
Security Assurance ◽  
Agile Software ◽  
Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Some Method Fragments for Agile Software Development

2009 ◽  
pp. 223-242
Author(s):  
Q. N.N. Tran ◽  
B. Henderson-Sellers ◽  
I. Hawryszkiewycz
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Method Engineering ◽  
Additional Method ◽  
Engineering Approach ◽  
Agile Methodologies ◽  
Process Framework ◽  
Australian Standard ◽  
Agile Software

The use of a situational method engineering approach to create agile methodologies is demonstrated. Although existing method bases are shown to be deficient, we take one of these (that of the OPEN Process Framework) and propose additional method fragments specific to agile methodologies. These are derived from a study of several of the existing agile methods, each fragment being created from the relevant powertype pattern as standardized in the Australian Standard methodology metamodel of AS 4651.

scholarly journals The Theory of One Team: Agile Software Development with Distributed Teams

2021 ◽  
Author(s):  
◽  
Siva Dorairaj
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Impact Factors ◽  
Distributed Teams ◽  
Agile Methods ◽  
Team Members ◽  
Software Companies ◽  
Distributed Team ◽  
The Usa ◽  
Agile Software

<p>Team co-location is a hallmark of Agile software development that advocates face-to-face interaction and close collaboration among team members. Distributed teams, however, use Agile methods despite the separation of team members through space, time and culture. Little is known about how distributed teams use Agile methods for software development. A Grounded Theory research study that involved 55 participants from 38 different software companies in the USA, India, and Australia was carried out to investigate the key concern of distributed teams in Agile software development. This thesis proposes “The Theory of One Team” which explains how a distributed team in Agile software development adopts explicit strategies for bridging spatial, temporal, and socio-cultural distances, while facing critical impact factors, in order to become one team. This thesis primarily describes how a distributed team resolves the key concern of becoming one team. This thesis also provides the members of a distributed team with techniques for building trust with one another. In addition, this thesis serves to inform senior managers about the importance of supporting distributed teams in Agile software development.</p>

scholarly journals The Theory of One Team: Agile Software Development with Distributed Teams

2021 ◽  
Author(s):  
◽  
Siva Dorairaj
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Impact Factors ◽  
Distributed Teams ◽  
Agile Methods ◽  
Team Members ◽  
Software Companies ◽  
Distributed Team ◽  
The Usa ◽  
Agile Software

<p>Team co-location is a hallmark of Agile software development that advocates face-to-face interaction and close collaboration among team members. Distributed teams, however, use Agile methods despite the separation of team members through space, time and culture. Little is known about how distributed teams use Agile methods for software development. A Grounded Theory research study that involved 55 participants from 38 different software companies in the USA, India, and Australia was carried out to investigate the key concern of distributed teams in Agile software development. This thesis proposes “The Theory of One Team” which explains how a distributed team in Agile software development adopts explicit strategies for bridging spatial, temporal, and socio-cultural distances, while facing critical impact factors, in order to become one team. This thesis primarily describes how a distributed team resolves the key concern of becoming one team. This thesis also provides the members of a distributed team with techniques for building trust with one another. In addition, this thesis serves to inform senior managers about the importance of supporting distributed teams in Agile software development.</p>

Sign in / Sign up

Export Citation Format

Share Document