Case Study Research in Software Engineering: Guidelines and Examples

APPENDIX D

EXAMPLE OF A CODING GUIDE

This appendix include an example of a coding guide from the REVV large-scale case study described in Chapter 14. The coding guide was used to help align the work among 11 involved researchers to minimize the validity threat of inconsistent coding application. The choice of the example included in the coding guide (Table D.5) was important in this alignment process.

D.1 CODING INSTRUCTIONS

• Code as much of the transcript as possible, even if you think that the text is not very relevant to “alignment.”¹ Since interviews are focused on alignment, everything said during interview could be useful for further analysis. Code questions as well.
• Codes are prioritized. Please use the priorities in the following way:
  • High level codes—assign the code with highest priority.
  • Medium level codes—choose the code that fits best. Since 2 columns are used for coding (“Primary code” and “Secondary code”), use the “Primary code” column for the code that fits best, and the “Secondary code” column for second best fitting code. If more than two codes are applicable—write it in “Comments” field.
• Use “Comments” field as much as possible. It can be used for
  • describing additional code categories (if code category is not in the list but you think it is important to have it);
  • listing other applicable codes;
  • explanations of “why” you chose particular code;
  • your interpretations of the text;
  • advices you may have for further analysis.

D.2 CODES

Transcripts should be coded ...