Integrating agile software development and software process improvement: a longitudinal case study

Author(s):  
O. Salo ◽  
P. Abrahamsson
Author(s):  
Sergio Galvan-Cruz ◽  
Manuel Mora ◽  
Rory V. O'Connor ◽  
Francisco Acosta ◽  
Francisco Álvarez

Software Process Improvement efforts (SPI) are pursued by organizations for improving the overall quality of their software development processes. However, very small entities (VSEs) avoid them by the lack of required financial and other organizational resources. In contrast, VSEs use agile software development methodologies (ASDMs), but these ASDMs do not foster adherence to best scholastic practices promoted by SPI. Furthermore, while a new ISO/IEC standard (29110) has been recently released for VSEs, it was not designed taking account the ASDM approaches. Thus, we investigate the extent of adherence of main ASDMs (two industrial and one academic type) with this new standard. Initial results provide evidence on the strong need to enhance the two industrial ASDMs (XP and SCRUM). In contrast, the academic ASDM (UPEDU) fits the standard very well but it is scarcely used by VSEs. Hence, it is concluded that there is a knowledge gap between the praxis with ASDMs and the recommended scholastic software processes like the ISO/IEC 29110 standard for VSEs.


Author(s):  
Hugo A. Mitre ◽  
Leonardo Bermon-Angarita

Currently, agile methods are replacing traditional process-based methods in the software industry. However, process-based software development still matters because of its degree of reusability in new projects. Some problems arise when Knowledge Management (KM) is not correctly aligned with processes, such as lack of productivity and process improvement. In this chapter, the authors present a case study of applying two proposals of process libraries in an agile software development division. The researchers and the software development division worked with a Kanban dashboard, eXtremme Programming (XP), and SCRUM practices, adapted to Process Assets Library (PAL) and to Process Practice Library (PPL) in three software projects in order to find experiences of tacit and explicit knowledge that have an impact on process improvement and productivity. Under results and discussion, the authors present the good and bad practices.


2016 ◽  
Vol 24 (3) ◽  
pp. 45-70 ◽  
Author(s):  
Delroy Chevers ◽  
Annette M. Mills ◽  
Evan Duggan ◽  
Stanford Moore

For software development firms to be competitive they must assure the quality of the software product. This has led many firms to adopt software process improvement (SPI) programs such as the capability maturity model integration (CMMI). However, for small software firms, especially those in developing countries with limited resources, these programs are often too cumbersome and costly to implement. To address this issue, this paper proposes a simplified SPI model for small firms (SPM-S) comprised of 10 key software development practices; with fewer practices, the proposed model should be more accessible and less costly to implement. Using data collected in four developing countries in the English-speaking Caribbean from 112 developer/user dyads, the model is evaluated with respect to its impact on software quality. The findings show that the software development process coupled with supporting technology (e.g. project management tools) significantly impact software product quality. Implications for software process improvement in small firms and future research are discussed.


Different models and standards have been developed with the purpose of improving software development processes and obtaining quality products and achieving customer satisfaction. Despite the efforts that organizations make, they do not always achieve these results. In this article we present the results of the implementation of best practices established by the CMMI model using the IDEAL and SCAMPI B methodology. The results show that applying best practices helps organizations to improve their processes, minimize the number of defects and increase customer satisfaction. Likewise, the critical factors that were considered and aspects to be considered in the deployment of processes are presented.


Sign in / Sign up

Export Citation Format

Share Document