Software Development Artifacts in Large Agile Organizations: A Comparison of Scaling Agile Methods

Author(s):  
Ewelina Wińska ◽  
Włodzimierz Dąbrowski
Author(s):  
Thatiane de Oliveira Rosa ◽  
Alfredo Goldman

Abstract In this document, we describe the experience of teaching Agile Methods for developing projects related to the Linux Kernel, during the XP Lab course. In 2018, the first project related to this context emerged. This project had the objective of making adjustments to the driver for Linux IIO subsystem. The second project was developed in 2019 and aimed to refactor the Ethernet driver used in the kernel of a Brazilian Single Board Computer. Based on 19 years of experience offering the XP Lab course, we consider the development of these projects to be a challenging teaching activity, which deserves to be presented and discussed with students, educators, and professionals. Our aim is to show that it is possible to adapt Agile Values to different software development settings.


2017 ◽  
Vol 48 (1) ◽  
pp. 3-18 ◽  
Author(s):  
Thomas G. Lechler ◽  
Siwen Yang

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.


Author(s):  
Zaidoun Alzoabi

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.


Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova

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.


Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen

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.


Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen

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.


Author(s):  
Boris Roussev

Agile methods are lightweight, iterative software development frameworks used predominantly on small and mid-sized software development projects. This chapter introduces a project structure and management practices creating agile conditions for large software projects outsourced either offshore or onshore. Agility is achieved by slicing a large project into a number of small projects working in agile settings. Development is divided into research and development activities that are located on-site, and production activities located off-site. The proposed approach makes agile methods applicable to the stressed conditions of outsourcing without compromising the quality or pace of the software development effort. Creating an agile environment in an outsourcing project relies on maintaining a balance between the functions and sizes of on-site and off-site teams, on redefining the developers’ roles, and on reorganizing the information flow between the different development activities to compensate for the lack of customers on-site, team colocation, and tacit project knowledge.


2015 ◽  
Vol 10 (4) ◽  
pp. 32-35
Author(s):  
Gerhard Müller ◽  
Gerold Quathamer ◽  
Christian Opel ◽  
Marius Lauder

Author(s):  
Wellington Feitoza Gonçalves ◽  
Ivaldir de Farias Junior ◽  
Renata Kalina de Paulo Alves ◽  
Pedro Luis Saraiva Barbosa ◽  
Herlon Ribeiro Parente Cortez ◽  
...  

Sign in / Sign up

Export Citation Format

Share Document