Eric Knauss

Eric Knauss

Auto-generated profile, based on publicly available information

Eric Knauss

University of Gothenburg

Research Focus & Metrics

Academic Career Length

19Years (2008-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
28 November 2009 in Requirements Engineering
Verified
Journal Article
Closed access
PDF file
SHSiv Hilde Houmb
Siv Hilde Houmb
Shareeful IslamShareeful Islam
Shareeful Islam
EKEric Knauss
Eric Knauss
JJJan Jürjens
Jan Jürjens
KSKurt Schneider
Kurt Schneider

26 July 2021 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
MKMarco Kuhrmann
Marco Kuhrmann
PTPaolo Tell
Paolo Tell
RHRegina Hebig
Regina Hebig
JKJil Klunder
Jil Klunder
JMJurgen Munch
Jurgen Munch
IRIta Richardson
Ita Richardson
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders’ collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15 percent). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

1 January 2011
Verified
Book Chapter
Closed access
PDF file
EKEric Knauss
Eric Knauss
SHSiv Houmb
Siv Houmb
KSKurt Schneider
Kurt Schneider
SIShareeful Islam
Shareeful Islam
JJJan Jürjens
Jan Jürjens

18 November 2019
Verified
Book Chapter
Closed access
PDF file
JSJan-Philipp Steghöfer
Jan-Philipp Steghöfer
EKEric Knauss
Eric Knauss
JHJennifer Horkoff
Jennifer Horkoff
RWRebekka Wohlrab
Rebekka Wohlrab

21 November 2018 in Requirements Engineering
Verified
Journal Article
Open access
PDF file
RWRebekka Wohlrab
Rebekka Wohlrab
EKEric Knauss
Eric Knauss
JSJan-Philipp Steghöfer
Jan-Philipp Steghöfer
SMSalome Maro
Salome Maro
AAAnthony Anjorin
Anthony Anjorin
PPPatrizio Pelliccione
Patrizio Pelliccione
Traceability is crucial for many activities in software and systems engineering including monitoring the development progress, and proving compliance with standards. In practice, the use and maintenance of trace links are challenging as artifacts undergo constant change, and development takes place in distributed scenarios with multiple collaborating stakeholders. Although traceability management in general has been addressed in previous studies, there is a need for empirical insights into the collaborative aspects of traceability management and how it is situated in existing development contexts. The study reported in this paper aims to close this gap by investigating the relation of collaboration and traceability management, based on an understanding of characteristics of the development effort. In our multiple exploratory case study, we conducted semi-structured interviews with 24 individuals from 15 industrial projects. We explored which challenges arise, how traceability management can support collaboration, how collaboration relates to traceability management approaches, and what characteristics of the development effort influence traceability management and collaboration. We found that practitioners struggle with the following challenges: (1) collaboration across team and tool boundaries, (2) conveying the benefits of traceability, and (3) traceability maintenance. If these challenges are addressed, we found that traceability can facilitate communication and knowledge management in distributed contexts. Moreover, there exist multiple approaches to traceability management with diverse collaboration approaches, i.e., requirements-centered, developer-driven, and mixed approaches. While traceability can be leveraged in software development with both agile and plan-driven paradigms, a certain level of rigor is needed to realize its benefits and overcome challenges. To support practitioners, we provide principles of collaborative traceability management. The main contribution of this paper is empirical evidence of how culture, processes, and organization impact traceability management and collaboration, and principles to support practitioners with collaborative traceability management. We show that collaboration and traceability management have the potential to be mutually beneficial—when investing in one, also the other one is positively affected.

16 September 2010
Verified
Conference Paper
Open access
NZNico Zazworka
Nico Zazworka
KSKai Stapel
Kai Stapel
EKEric Knauss
Eric Knauss
FSForrest Shull
Forrest Shull
VBVictor R. Basili
Victor R. Basili
KSKurt Schneider
Kurt Schneider
Adapting new software processes and practices in organizational and academic environments requires training the developers and validating the applicability of the newly introduced activities. Investigating process conformance during training and understanding if programmers are able and willing to follow the specific steps are crucial to evaluating whether the process improves various software product quality factors. In this paper we present a process model independent approach to detect process non-conformance. Our approach is based on non-intrusively collected data captured by a version control system and provides the project manager with timely updates. Further, we provide evidence of the applicability of our approach by investigating process conformance in a five day training class on eXtreme Programming (XP) practices at the Leibniz Universität Hannover. Our results show that the approach enabled researchers to formulate minimal intrusive methods to check for conformance and that for the majority of the investigated XP practices violations could be detected.