scispace - formally typeset
Search or ask a question
Journal ArticleDOI

Case Study Research

About: This article is published in Journal of Wound Ostomy and Continence Nursing.The article was published on 1999-03-01. It has received 6069 citations till now.
Citations
More filters
Journal ArticleDOI
TL;DR: In this paper, the use of case study research in operations management for theory development and testing is reviewed and guidelines and a roadmap for operations management researchers wishing to design, develop and conduct case-based research are provided.
Abstract: This paper reviews the use of case study research in operations management for theory development and testing. It draws on the literature on case research in a number of disciplines and uses examples drawn from operations management research. It provides guidelines and a roadmap for operations management researchers wishing to design, develop and conduct case‐based research.

4,127 citations


Cites background or methods from "Case Study Research"

  • ...The reliability[2] and validity of case research data will be enhanced by a well-designed research protocol (Yin 1994)....

    [...]

  • ...Leonard-Barton (1990) compares the necessary interviewing skills with those of an investigative reporter....

    [...]

  • ...Yin (1994) has described in detail case research design, and Glaser and Strauss (1967) described the grounded theory method....

    [...]

  • ...Experiment Quasi-experiment Multiple case studies Large-scale sample of population...

    [...]

  • ...In studies involving a large number of sites where multiple single interviewers are used, it is important that early interviews are done in pairs or teams....

    [...]

Journal ArticleDOI
TL;DR: An approach based on ‘systematic combining’ grounded in an ‘abductive’ logic is suggested for single case research aiming at theory development in industrial network research.

4,121 citations


Cites background or result from "Case Study Research"

  • ...Yin (1994) is critical of some case study research, stating that ‘‘too many times the case study investigator has been sloppy and has allowed equivocal evidence on biased views to influence the direction of the findings and conclusions.’’...

    [...]

  • ...The main arguments against it have been that case studies provide little basis for scientific generalization (Yin, 1994). For example, Weick (1969, p. 18) >expresses the opinion that case studies are too situationspecific and, therefore, not appropriate for generalization. In the second edition of the same book, however, he concludes, with reference to ‘noted investigators’, that case studies ‘‘are better tools than first imagined’’ (Weick, 1979, p. 37). The reason for the revised attitude to case studies was an evolving insight that ‘‘findings are unstable over time.’’ Weick (1979, p. 37) recommends, in line with Cronbach (1975), that researchers should ‘‘try harder to make interpretations specific to situations....

    [...]

  • ...The main arguments against it have been that case studies provide little basis for scientific generalization (Yin, 1994)....

    [...]

  • ...According to Yin (1994), it is applied extensively in as widely ranging subject areas as psychology, sociology, political science, anthropology, history, economics, urban planning, public administration, public policy, management, social work, and education....

    [...]

  • ...Combining sources of evidence, while shifting between analysis and interpretation, usually denotes triangulation (Yin, 1994; Denzin, 1978)....

    [...]

Journal ArticleDOI
TL;DR: This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies, and presents recommended practices and evaluated checklists for researchers and readers of case study research.
Abstract: Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors' own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.

3,620 citations


Cites background or methods or result from "Case Study Research"

  • ...the case is selected to predict contrasting results for predictable reasons (Yin 2003)....

    [...]

  • ...Case study methodology handbooks are superfluously available in e.g. social sciences (Robson 2002; Stake 1995; Yin 2003) which literature also has been used in software engineering....

    [...]

  • ...5 we discuss specific data collection methods, where we have found interviews, observations, archival data and metrics being applicable to software engineering case studies (Benbasat et al. 1987; Yin 2003)....

    [...]

  • ...social sciences (Robson 2002; Stake 1995; Yin 2003) which literature also has been used in software engineering....

    [...]

  • ...Yin proposes several alternative structures for reporting case studies in general (Yin 2003)....

    [...]

Journal ArticleDOI
TL;DR: In this article, a study of 11 capital equipment manufacturers developing service offerings for their products is presented, focusing on identifying the dimensions considered when creating a service organization in the context of a manufacturing firm, and successful strategies to navigate the transition.
Abstract: Management literature is almost unanimous in suggesting to manufacturers that they should integrate services into their core product offering. The literature, however, is surprisingly sparse in describing to what extent services should be integrated, how this integration should be carried out, or in detailing the challenges inherent in the transition to services. Reports on a study of 11 capital equipment manufacturers developing service offerings for their products. Focuses on identifying the dimensions considered when creating a service organization in the context of a manufacturing firm, and successful strategies to navigate the transition. Analysis of qualitative data suggests that the transition involves a deliberate developmental process to build capabilities as firms shift the nature of the relationship with the product end‐users and the focus of the service offering. The report concludes identifying implications of our findings for further research and practitioners.

2,267 citations


Cites background or methods from "Case Study Research"

  • ...With very few exceptions (e.g. General Electric, ABB, Otis, Caterpillar, etc.), the manufacturers’ transition into services has been relatively slow and cautious (VDMA, 1998)....

    [...]

  • ...To explore ®rms’ transitions, we employed an inter-disciplinary research approach that included interviews, and a detailed archival assessment of the organizations’ experience in integrating services into their product offering (Eisenhardt, 1989; Yin, 1984)....

    [...]

Journal ArticleDOI
Yves L. Doz1
TL;DR: Analysis of the evolution of strategic alliances helps transcend too simple depictions of inertia and adaptation by suggesting that initial conditions may lead to a stable 'imprinting' of fixed processes that make alliances highly inertial or to generative and evolutionary processes that makes them highly adaptive, depending on how they are set.
Abstract: We examine how the learning, along several dimensions (environment, task, process, skills, goals), that takes place in strategic alliances between firms mediates between the initial conditions and the outcomes of these alliances. Through a longitudinal case study of two projects in one alliance, replicated and extended in another four projects in two alliances, a framework was developed to analyze the evolution of cooperation in strategic alliances. Successful alliance projects were highly evolutionary and went through a sequence of interactive cycles of learning, reevaluation and readjustment. Failing projects, conversely, were highly inertial, with little learning, or divergent learning between cognitive understanding and behavioral adjustment, or frustrated expectations. Although strategic alliances may be a special case of organizational learning, we believe analyzing the evolution of strategic alliances helps transcend too simple depictions of inertia and adaptation, in particular by suggesting that initial conditions may lead to a stable 'imprinting' of fixed processes that make alliances highly inertial or to generative and evolutionary processes that make them highly adaptive, depending on how they are set.

2,236 citations


Cites methods from "Case Study Research"

  • ...The other cases (AT&TOlivetti, GE-SNECMA) were added to the sample as theoretical replications and extensions (Yin, 1984; Leonard-Barton, 1990) to challenge and refine the initial framework....

    [...]