Managing Change in Software Process Improvement

Mathiassen, Lars; Ngwenyama, Ojelanki; Aaen, Ivan

doi:10.1109/ms.2005.159

Cited by 72 publications

(60 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…[25][26] [27]) have analysed the management of requirements change. These studies analysed changes in terms of their cause, type, implementation and verification.…”

Section: Related Workmentioning

confidence: 99%

An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry

Hotomski

Charrada

Glinz

2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

With the emergence and spread of agile processes, the practices of writing and maintaining documentation have drastically changed in the last decade. In this work, we performed a qualitative study to explore the current practices for managing two related types of software documentation: requirements and acceptance tests. We interviewed twenty practitioners from seventeen business units in fifteen companies to investigate the companies' practices for writing, maintaining and linking requirements and acceptance test documentation. The study yields interesting and partially unexpected results. For example, we had expected that tests would be more extensively documented than requirements, while we found a strong linear correlation between the number of requirements and tests in our sample. We also found that technical people are usually not involved in the requirements engineering activities, which often results in misunderstood or underestimated requirements. Acceptance tests are written, in many cases, based on requirements that are not necessarily detailed enough. Also, acceptance tests are not regularly maintained, which occasionally results in confusing features and bugs. Abstract-With the emergence and spread of agile processes, the practices of writing and maintaining documentation have drastically changed in the last decade. In this work, we performed a qualitative study to explore the current practices for managing two related types of software documentation: requirements and acceptance tests. We interviewed twenty practitioners from seventeen business units in fifteen companies to investigate the companies' practices for writing, maintaining and linking requirements and acceptance test documentation. The study yields interesting and partially unexpected results. For example, we had expected that tests would be more extensively documented than requirements, while we found a strong linear correlation between the number of requirements and tests in our sample. We also found that technical people are usually not involved in the requirements engineering activities, which often results in misunderstood or underestimated requirements. Acceptance tests are written, in many cases, based on requirements that are not necessarily detailed enough. Also, acceptance tests are not regularly maintained, which occasionally results in confusing features and bugs.

show abstract

“…[25][26] [27]) have analysed the management of requirements change. These studies analysed changes in terms of their cause, type, implementation and verification.…”

Section: Related Workmentioning

confidence: 99%

An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry

Hotomski

Charrada

Glinz

2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

show abstract

“…SPI researchers have focused on a wide variety of problems and challenges confronting organizations engaging in SPI [1], [22]. While there is general agreement that SPI is associated with considerable organizational changes both in terms of scale and complexity [40], organizational issues have been inadequately prioritized in the SPI literature and our current knowledge is therefore insufficient [47], [41].…”

Section: Introductionmentioning

confidence: 99%

Managing Cultural Variation in Software Process Improvement: A Comparison of Methods for Subculture Assessment

Müller

Kræmmergaard

Mathiassen

2009

IEEE Trans. Eng. Manage.

View full text Add to dashboard Cite

“…Designing a SPI study requires considering the following specificity of software organizations [16]: (1) process improvement aims at improving products and services, (2) evaluation of improvement results is necessary for directing further activities, (3) improvement should be seen as a continuous learning cycle in an organization, and (4) improvement results and experiences should be systematized for future projects. 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.…”

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

Managing Change in Software Process Improvement

Cited by 72 publications

References 3 publications

An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry

An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry

Managing Cultural Variation in Software Process Improvement: A Comparison of Methods for Subculture Assessment

Inductive Approaches in Software Process Assessment

Contact Info

Product

Resources

About