ABSTRACT
Case study research has become an important research methodology for exploring phenomena in their natural contexts. Case studies have earned a distinct role in the empirical analysis of software engineering phenomena which are difficult to capture in isolation. Such phenomena often appear in the context of methods and development processes for which it is difficult to run large, controlled experiments as they usually have to reduce the scale in several respects and, hence, are detached from the reality of industrial software development. The other side of the medal is that the realistic socio-economic environments where we conduct case studies -- with real-life cases and realistic conditions -- also pose a plethora of practical challenges to planning and conducting case studies. In this experience report, we discuss such practical challenges and the lessons we learnt in conducting case studies in industry. Our goal is to help especially inexperienced researchers facing their first case studies in industry by increasing their awareness for typical obstacles they might face and practical ways to deal with those obstacles.
- S. Adolph, W. Hall, and P. Kruchten. Using Grounded Theory to study the Experience of Software Development. Journal of Empirical Software Engineering, 16(4), 2011. Google ScholarDigital Library
- A. A. Amschler and A. S. Pradhan. Ethical issues in empirical software engineering: The limits of policy. Empirical Software Engineering, 6(2):105--110, 2001. Google ScholarDigital Library
- V. Basili. A Personal Perspective on the Evolution of Empirical Software Engineering. In J. Muench and K. Schmid, editors, Perspectives on the Future of Software Engineering, pages 255--273. Springer, 2013.Google ScholarCross Ref
- N. Carayol. Objectices, Agreements and Matching in Science-Industry Collaborations: Reassembling the Pieces of the Puzzle. Research Policy, 32:887--908, 2003.Google ScholarCross Ref
- P. Diebold, A. Vetrò, and D. Méndez Fernández. An Exploratory Study on Technology Transfer in Software Engineering. In Proc. 9th International Symposium on Empirical Software Engineering and Measurement. IEEE, 2015.Google ScholarCross Ref
- I. Jacobson and I. Spence. Why we need a Theory for Software Engineering. Dr. Dobb's Journal, 2009.Google Scholar
- M. Junker, M. Broy, B. Hauptmann, W. Boehm, H. Femmer, S. Eder, E. Juergens, and R. Janssen. Principles and a Process for Successful Industry Cooperation -- The Case of TUM and Munich Re. In Proc. Intl. Workshop on Software Engineering Research and Industrial Practice. IEEE, 2015. Google ScholarDigital Library
- G. Kalus and M. Kuhrmann. Criteria for Software Process Tailoring: A Systematic Review. In Proc. 8th International Conference on Global Software Engineering. ACM, 2013.Google ScholarDigital Library
- D. Méndez Fernández, J. Mund, H. Femmer, and A. Vetrò. In Quest for Requirements Engineering Oracles: Dependent Variables and Measurements for (good) RE. In Proc. 18th International Conference on Evaluation and Assessment in Software Engineering. ACM, 2014. Google ScholarDigital Library
- D. Méndez Fernández, S. Wagner, K. Lochmann, A. Baumann, and H. de Carne. Field Study on Requirements Engineering: Investigation of Artefacts, Project Parameters, and Execution Strategies. Information and Software Technology, 54(2):162--178, 2012. Google ScholarDigital Library
- P. Runeson and M. Höst. Guidelines for Conducting and Reporting Case Study Research in Software Engineering. Empirical Software Engineering, 14(2):131--164, 2009. Google ScholarDigital Library
- P. Runeson, M. Höst, A. Rainer, and B. Regnell. Case Study Research in Software Engineering: Guidelines and Examples. Wiley, 2012. Google ScholarDigital Library
- J. M. Verner, J. Sampson, V. Tosic, N. A. A. Bakar, and B. A. Kitchenham. Guidelines for Industrially-based Multiple Case Studies in Software Engineering. In Proc. Third International Conference on Research Challenges in Information Science. IEEE, 2009.Google ScholarCross Ref
- A. Vetro, S. Ognawala, D. Méndez Fernández, and S. Wagner. Fast Feedback Cycles in Empirical Software Engineering Research. In Proc. 37th International Conference on Software Engineering. IEEE, 2015. Google ScholarDigital Library
- Wagner, S. and Mendez Fernandez, D. Analysing Text in Software Projects. In Bird, C. and Menzies, T. and Zimmermann, T., editor, The Art and Science of Analyzing Software Data. Morgan Kaufmann, 2015.Google Scholar
- R. Wieringa. Empirical Research Methods for Technology Validation: Scaling up to Practice. Journal of Systems and Software, 95:19--31, 2013. Google ScholarDigital Library
- R. Wieringa and M. Aycse. Technical Action Research as a Validation Method in Information Systems Design Science. In Proc. 7th International Conference on Design Science Research in Information Systems: Advances in Theory and Practice. Springer, 2012. Google ScholarDigital Library
- R. K. Yin. Case Study Research. Sage Publications, 2013.Google Scholar
Index Terms
- Case studies in industry: what we have learnt
Recommendations
The Combination of Agile and Lean in Software Development: An Experience Report Analysis
AGILE '11: Proceedings of the 2011 Agile ConferenceThere has been a noticeable focus shift from agile methods such as extreme Programming (XP) and Scrum to lean software development in the last several years, which is indicated as â from agile to leanâ . However, the reality may not be as simple or ...
"Leagile" software development
In recent years there has been a noticeable shift in attention from those who use agile software development toward lean software development, often labelled as a shift "from agile to lean". However, the reality may not be as simple or linear as this ...
Lean Transformation: Adapting to the change, factors for success and lessons learnt during the journey: A case study in a multi location software product development team
ISEC '16: Proceedings of the 9th India Software Engineering ConferenceA team of 400+ which followed V-model lifecycle underwent a dramatic transformation by adapting the Lean Product Development Lifecycle in 2010. The transformation began with a pilot project, based on whose experience; Lean was scaled to other projects ...
Comments