A Detailed Software Process Improvement Methodology: BG-SPI

Aysolmaz, Banu; Demirörs, Onur

doi:10.1007/978-3-642-22206-1_9

Cited by 19 publications

(17 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Software organizations vary widely, and each SPI initiative requires managers to be sensitive to the context of change introduced through SPI implementation by considering [37]: motivation for SPI, overall SPI strategy, stakeholders, current practice, and interactions with customers. Several studies reported that standard based SPI approaches, such as SCAMPI [54], SPICE [29] or ISO 9001:2015 [61], are inappropriate for the actual processes or context in small software organizations, leading to development of lightweight approaches, such as TAPISTRY [34], COMPETISOFT [47] or BG-SPI [6], that are suitable for them. In addition, ISO organization developed a standard ISO 29110 Software engineering -Lifecycle profiles for Very Small Entities (VSEs) [30] which is version of ISO 12207 Systems and software engineering -Software life cycle processes [28], tailored for small organizations.…”

Section: Software Process Improvementmentioning

confidence: 99%

Inductive Approaches in Software Process Assessment

Stojanov

2016

Proccedings of the ICAIIT2016

View full text Add to dashboard Cite

Abstract. Software processes play important role in overall business performances of software organizations. However, in many cases processes are not well established, leading to poor performances of software products and services. Since majority of software organizations are small, suffering from the lack of resources, there is a permanent need for developing lightweight inductive approaches for assessing and improving their processes. These approaches should start from the actual state of the practice in software organizations, and result with the most suitable improvement proposals. This paper presents a short introduction into software processes, process assessment and improvement, and motivation for investigating the field of inductive software process assessment. The paper also outlines basic principles of inductive assessment approaches and future challenges.

show abstract

Section: Software Process Improvementmentioning

confidence: 99%

Inductive Approaches in Software Process Assessment

Stojanov

2016

Proccedings of the ICAIIT2016

View full text Add to dashboard Cite

show abstract

“…Other studies have identified that the characteristics of the SPI models can limit the success of SPI initiatives in small organizations. In their study, Demirors and Demirors identified several difficulties related to SPI models.…”

Section: Related Workmentioning

confidence: 99%

“…In addition, several studies have identified human and social issues that small organizations need to consider during their SPI initiatives . In their study, Demirors and Demirors identified several issues related to the employees of small organizations.…”

Section: Related Workmentioning

confidence: 99%

Understanding SPI in small organizations: a study of Mexican software enterprises

Espinosa-Curiel

Rodríguez-Jacobo

Fernández-Zepeda

2016

J Software Evolu Process

View full text Add to dashboard Cite

Software process improvement (SPI) has become one of the main strategies employed by small software enterprises to reduce their development costs or to increase the quality of their products and their development speed. Recent studies show that many small organizations still struggle to implement SPI initiatives successfully. One of the main problems with small organizations is that they usually lack the knowledge and practical experience about the human, social, and organizational phenomena associated with SPI initiatives and their effects. The objective of this paper is to present a grounded action research study that investigated SPI initiatives conducted by 10 Mexican small enterprises. The main product of this study is an initial theoretical framework that attempts to explain the effects of SPI initiatives in small organizations. We concluded that SPI initiatives affect organizational elements (i.e., structure, culture, organizational climate, projects) and human resources (i.e., employees and managers), and vice versa, and these elements are highly interrelated. Therefore, small enterprises need comprehensive SPI strategies that consider, in an integrated way, changes in processes, organizational elements, and human resources. SPI practitioners can use the results of this study to define more efficient and effective strategies to implement SPI initiatives in small organizations.

show abstract

“…Discussion on their strengths and weaknesses are the subject of much research, e.g., from [3,5,15]. Light-weight SPI models, such as PRO-CESSUS [8], LAPPI [14], COMPETISOFT [7], or BG-SPI [2] usually address small-to-medium sized companies and provide detailed guideline regarding the approach to conduct SPI. However, if these models define artifacts they usually just name the artifacts and give examples, but omit detailed structure and dependencies.…”

Section: Related Workmentioning

confidence: 99%

“…reliability. A number of standardized SPI approaches exist to support process engineers in managing SPI, e.g., reference models such as CMMI [4] or ISO 15504 [9], as well as more specific and light-weight SPI models, e.g., LAPPI [14], or BG-SPI [2]. However, process engineers and process consumers often complain about approaches that are too generic, too comprehensive, or that are inappropriate for the actual project or company context [15].…”

Section: Introductionmentioning

confidence: 99%

Artifact-based software process improvement and management: a method proposal

Kuhrmann¹,

Beecham

2014

Proceedings of the 2014 International Conference on Software and System Process

View full text Add to dashboard Cite

When it comes to software process improvement (SPI), process engineers look for SPI methods to support process analysis, design, realization, deployment, and management. Although a number of different SPI methods and models exist, process engineers tend to view these as too generic, too large, or a poor fit for the organization in which SPI is conducted. A strategy to overcome these shortcomings is to concentrate on the artifacts, which precisely define the desired outcomes, rather than on specific methods. In this paper, we present the Artifact-based Software Process Improvement & Management (ArSPI) model that provides a unified perspective on SPI and company-wide software process management (SPM), the required key artifacts, and the life cycle models. ArSPI is shown to be of practical support to industry who called for a practical way to define the interfaces between SPI projects. This paper concludes with an example of how ArSPI paved the way for several organizations through applying the model in real-world SPIprojects.

show abstract

A Detailed Software Process Improvement Methodology: BG-SPI

Cited by 19 publications

References 12 publications

Inductive Approaches in Software Process Assessment

Inductive Approaches in Software Process Assessment

Understanding SPI in small organizations: a study of Mexican software enterprises

Artifact-based software process improvement and management: a method proposal

Contact Info

Product

Resources

About