Establishing experience factories at Daimler-Benz an experience report

Houdek, Frank; Schneider, Kurt; Wieser, Eva

doi:10.1109/icse.1998.671602

Cited by 33 publications

(16 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since the experience factory group aims to generalize as much project experiences as possible for re-use, to bootstrap or to update the content in an experience repository need to undergo a controlled and often slow process. In addition, most reports on experience factories stem from large organizations that can afford to create centralized organizational units for organizational learning [2,20,14]. However, such resources may not be available to smalland medium-sized software companies.…”

Section: Introductionmentioning

confidence: 99%

“…Despite the substantial number of Experience Factory implementations cited in the literature, there are few evaluations on the use of such knowledge repositories. Of the few experience reports and case studies, the study contexts are often in large organizations such as NASA [2], Daimler Chrysler [20,14], and Ericsson [16], or the knowledge repositories studied are only based on either the codification strategy [2,20,14] or the personalization strategy [16] but not both. In comparison, the context in our case study is in a medium-sized software organization where teams are geographically distributed.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A case study of wiki-based experience repository at a medium-sized software company

Chau

Maurer

2005

Proceedings of the 3rd International Conference on Knowledge Capture

View full text Add to dashboard Cite

The paper reports on an exploratory case study where an organizational learning methodology was used to support knowledge sharing in a medium-sized distributed software development company. The method is based not only on a codification approach but also on a personalization strategy. To facilitate its use in a dynamic environment with minimal overhead, our MASE system utilizes both informal and formal knowledge representation mechanisms. The results provide evidences for the need of knowledge sharing tools (1) to incorporate not only codification-oriented repository technologies but also those that facilitate communication and collaboration among people, and (2) to support not only structured but also unstructured knowledge representation mechanism. It reveals that an informal knowledge authoring tool such as the Wiki-based MASE is used for sharing content for problem understanding, instrumental, projective, social, expertise location, and content navigation purposes. We also observe self-organized maintenance of the repository content among the ordinary repository users as a result of the open-edit nature of MASE.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

A case study of wiki-based experience repository at a medium-sized software company

Chau

Maurer

2005

Proceedings of the 3rd International Conference on Knowledge Capture

View full text Add to dashboard Cite

show abstract

“…Most of the work that has been reported on knowledge management in the software engineering literature (often referred to as work on "experience factory") are from large organizations, such as Daimler Chrysler [3,4], The NASA Software Engineering Laboratory [5] and Ericsson [6]. See.J7] for an overview.…”

Section: Introductionmentioning

confidence: 99%

An Empirical Study of an Informal Knowledge Repository in a Medium-Sized Software Consulting Company

2006

Software Process Improvement

View full text Add to dashboard Cite

show abstract

“…More recent papers drawing on the earlier work (Schneider et al, 2002;Houdek et al, 1998) describe DaimlerChrysler's implementation of an Experience Center in software engineering. These ideas have now spread widely; for an Australian example see (Koennecker et al, 1999), and see also (Brössler, 1999;Chatters, 1999).…”

Section: Learning and Experience In Software Engineeringmentioning

confidence: 99%

Managing Software Engineers and Their Knowledge

Edwards¹

2003

Managing Software Engineering Knowledge

View full text Add to dashboard Cite

This chapter begins by reviewing the history of software engineering as a profession, especially the so-called "software crisis" and responses to it, to help focus on what it is that software engineers do. This leads into a discussion of the areas in software engineering that are problematic, as a basis for considering the knowledge management issues. Some of the previous work on knowledge management in software engineering is then examined, much of it not actually going under a "knowledge management" title, but rather "learning" or "expertise". The chapter goes on to consider the potential for knowledge management in software engineering, and the different types of knowledge management solutions and strategies that might be adopted, and touches on the crucial importance of cultural issues. It concludes with a list of challenges that knowledge management in software engineering needs to address.

show abstract

Establishing experience factories at Daimler-Benz an experience report

Cited by 33 publications

References 8 publications

A case study of wiki-based experience repository at a medium-sized software company

A case study of wiki-based experience repository at a medium-sized software company

An Empirical Study of an Informal Knowledge Repository in a Medium-Sized Software Consulting Company

Managing Software Engineers and Their Knowledge

Contact Info

Product

Resources

About