TY - GEN
T1 - Experience of Industry Case Studies
T2 - 6th ACM/IEEE International Workshop on Conducting Empirical Studies in Industry, CESI 2018, held at the 40th International Conference on Software Engineering, ICSE 2018
AU - Bass, Julian M.
AU - Lero, Sarah Beecham
AU - Noll, John
N1 - Publisher Copyright:
© 2018 Association for Computing Machinery.
PY - 2018/5/28
Y1 - 2018/5/28
N2 - Context: Case studies are a useful approach for conducting empirical studies of software engineering, in part because they allow a phenomenon to be studied in its real-world context. However, given that there are several kinds of case studies, each with its own strengths and weaknesses, researchers need to know how to choose which kind to employ for a specific research study. Aim: The objective of this research is to compare two case study approaches: Embedded, longitudinal case studies, and multi-case studies. Approach: We compared two actual software engineering case studies: A multi-case study involving interviews with 46 practitioners at 9 international companies engaged in offshoring and outsourcing, and a single case, participant observation embedded case study lasting 13 months in a mid-sized Irish software company. Both case studies were exploring similar problems of understanding the activities performed by members of scrum development teams. Results: We found that both multi-case and embedded case studies are suitable for exploratory research (hypothesis development) but that embedded research may also be more suitable for explanatory research (hypothesis testing).We also found that longitudinal case studies offer better confirmability, while multi-case studies offer better transferability. Conclusion: We propose a set of illustrative research questions to assist with the selection of the appropriate case study method.
AB - Context: Case studies are a useful approach for conducting empirical studies of software engineering, in part because they allow a phenomenon to be studied in its real-world context. However, given that there are several kinds of case studies, each with its own strengths and weaknesses, researchers need to know how to choose which kind to employ for a specific research study. Aim: The objective of this research is to compare two case study approaches: Embedded, longitudinal case studies, and multi-case studies. Approach: We compared two actual software engineering case studies: A multi-case study involving interviews with 46 practitioners at 9 international companies engaged in offshoring and outsourcing, and a single case, participant observation embedded case study lasting 13 months in a mid-sized Irish software company. Both case studies were exploring similar problems of understanding the activities performed by members of scrum development teams. Results: We found that both multi-case and embedded case studies are suitable for exploratory research (hypothesis development) but that embedded research may also be more suitable for explanatory research (hypothesis testing).We also found that longitudinal case studies offer better confirmability, while multi-case studies offer better transferability. Conclusion: We propose a set of illustrative research questions to assist with the selection of the appropriate case study method.
UR - http://www.scopus.com/inward/record.url?scp=85050724079&partnerID=8YFLogxK
U2 - 10.1145/3193965.3193967
DO - 10.1145/3193965.3193967
M3 - Conference contribution
AN - SCOPUS:85050724079
T3 - Proceedings - International Conference on Software Engineering
SP - 13
EP - 20
BT - Proceedings 2018 ACM/IEEE 6th International Workshop on Conducting Empirical Studies in Industry, CESI 2018
PB - IEEE Computer Society
Y2 - 28 May 2018
ER -