Applying ISO/IEC 12207:2008 with SCRUM and Agile Methods

Irrazábal, Emanuel; Vásquez, Felipe; Díaz, Ramón; Garzás, Javier

doi:10.1007/978-3-642-21233-8_15

Cited by 11 publications

(5 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One potential area could be integration of agile methods into process standards designed for small companies such as ISO/IEC 29110. For example, the work by Irrazabal et al [23] advocates for such integration for process assessment and improvement in small companies. Another option could be an automatic acquisition/extraction of evidences of process implementation instead of requiring organizations to avail work products for assessors which is documentation intensive.…”

Section: Discussionmentioning

confidence: 97%

Software Process Practices in Small Software Companies in Botswana

Ayalew

Motlhala

2014

2014 14th International Conference on Computational Science and Its Applications

View full text Add to dashboard Cite

In recognizing the potential that software can help in the socio-economic development of the country, the government of Botswana has identified software industry as one of the strategic priority areas in ICT with research focus on areas such as software engineering practices and software process improvement. To realize this vision, the state of software development practice has to be formally assessed to determine the strengths and weaknesses thereby providing input for the development of appropriate software development strategy for the country. However, the current state of software process practice has not yet been properly investigated. In this paper, we discuss the results of our study conducted to determine process performance and process capability of major software companies. The process assessment study was conducted following the METvalCOMPETISOFT assessment methodology. Our findings highlight the organizations' current software engineering practices by identifying strengths, major weaknesses and key areas for software process improvement. We also discuss our lightweight prototype tool developed for the management of process assessment in small companies.

show abstract

Section: Discussionmentioning

confidence: 97%

Software Process Practices in Small Software Companies in Botswana

Ayalew

Motlhala

2014

2014 14th International Conference on Computational Science and Its Applications

View full text Add to dashboard Cite

show abstract

“…This compliance problem between process standards or models with SDMs has been studied previously (Gallagher & Brownsword, 2001;Manzoni & Price, 2003;Mora et al, 2010;Irrazabal et al, 2011;Pasini et al, 2013;FernandezMonteiro, 2014;Larrucea & Santamaria, 2015;Cruz et al, 2015;Garcia et al, 2016) with the aim to help to organizations in achieving a satisfactory implementation and certification of the selected software process standard or model (Larrucea et al, 2016).…”

Section: Introductionmentioning

confidence: 89%

An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

Galván-Cruz

Mora

O’Connor

et al. 2017

International Journal of Information Technologies and Systems Approach

View full text Add to dashboard Cite

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.

show abstract

“…all except one paper was less than ten years of age. [39], Irrazabal et al [40], Hoda et al [41], [42], Dorairaj et al [43], Senapathi et al [44], Ressin et al [45], [46], Santos and Goldman [47], Kim and Ryoo [48], Ihme [49], and Allisy-Roberts et al [4], with publication years ranging from 2008 to 2017. Of the listed challenges, the one that is very peculiar comes from the mixed mode study by Heikkila et al [18], which recorded that cross functional generalist teams were not plausible in the environment.…”

Section: Scrum Adoption Challengesmentioning

confidence: 99%

Scrum Adoption Challenges Detection Model: SACDM

Hanslo¹,

Mnkandla²

2018

Proceedings of the 2018 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Scrum has been the most widely adopted Agile methodology over the past decade with Scrum and Scrum variants offering alternatives to the old software development methods. While Scrum plays an important role in the success of Agile development, it does come with its own challenges. In previous research challenges have been analyzed at the organizational and team level, primarily via case studies. However, fundamentally, Scrum needs to be adopted at the individual level. Furthermore, challenges such as inexperience, poor communication, specialization, lack of teamwork, low-quality, organizational culture and Scrum compatibility, have been identified as contributors. This paper therefore discusses the Scrum and Agile adoption challenges faced both globally as well as within the South African borders, from the findings of a narrative review. Secondly, a custom model adapted from the Diffusion of Innovation theoretical model was developed to detect the Scrum adoption challenges experienced within software organizations at the individual level. The custom model referred to as the Scrum Adoption Challenges Detection Model (SACDM) consists of four constructs, namely; individual factors, team factors, organizational factors and technology factors. The constructs are composed of nineteen independent variables that assists in understanding which factors contributes towards an individual either adopting or rejecting Scrum within a software organization. SACDM is therefore used to detect the adoption or rejection of Scrum as the dependent variable based on the independent variables being tested within the four constructs. The model can further be used with a survey questionnaire to provide generalized awareness of Scrum adoption challenges allowing software organizations to make more informed decisions when adopting Scrum. Future research is to allow the model to contribute towards Scrum adoption challenges predictive analysis.

show abstract

Applying ISO/IEC 12207:2008 with SCRUM and Agile Methods

Cited by 11 publications

References 20 publications

Software Process Practices in Small Software Companies in Botswana

Software Process Practices in Small Software Companies in Botswana

An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

Scrum Adoption Challenges Detection Model: SACDM

Contact Info

Product

Resources

About