Data and Material for 'Interpersonal Conflicts During Code Review'

## About the study

This study was exploring the landscape of interpersonal conflicts during code review in following areas:
- how these conflicts look like
- what role do they play in software development
- what are their consequences
- what factors do play role in their appearance and severity
- what strategies can be used to prevent and manage conflicts


## Methodology

The study collected 22 interviews with developers. Using qualitative thematic analysis, the authors analysed the anonymised interviews for the form and context of interpersonal conflicts during code review and potential strategies to prevent and manage them. The analysis was conducted in NVivo 12, a software for qualitative analysis.

To support validity of the analysis, it was revised through an "Audit Trail" like process. The analysis, study methodology and results have been examined by a senior researcher within the team. The files included in the audit are included in this folder as well.


## Dataset Content
-----------------
This folder contains online material for the study clarifying and extending information for reviewers and readers interested in the methodology. 

- `README.txt` - information on the content and purpose of this online material

### The Analysis
- `conflicts_analysis.nvpx` - NVivo 12 file containing the complete results, transcripts, codings and definitions used and created throught the analysis
- `definitions.pdf` - definitions of the final higher themes identified in the analysis
- `codes.pdf` - complete list of codes and themes coded during the analysis

### Supplementary documents:
- `sample_descriptives.pdf` - Description of individual participants and their characteristics
- `interview_structure.pdf` - Structure of the interviews conducted in the study
- `participant_consent_form.pdf` - Participant Consent that has been signed by the participants in the study
- `transcripts.pdf` - a file containing the complete set of anonymised transcripts
- `Audit` - Folder containing files submitted for the Audit Trail except of files constant throughout the study like Participant Consent or Transcripts of the interviews.


Audit Trail
-----------------
Audit trail is a procedure to validate results of qualitative analysis. It requires the researcher to provide detailed information on how they conducted the analysis to auditors external to the analysis. The goal of a formal audit is to examine both the process and product of the inquiry, and determine the trustworthiness of the findings. This folder contains files to perform the audit trail for the study.

Goal
-----------------
The goal of the audit is:
- to get acquainted with the methodology and results of the analysis and related documentation
- to review whether the results of the analysis are a good representation of the data
- to review whether the analysis does not breach knowledge available to software engineering, unless well supported
- to review whether the results are useful for the community
- to control for issues and shortcomings of the analysis

Files
-----------------
The "Audit" folder contains following files (We recommend reviewing them in this order):
- analysisplan_results.pdf - text summarising background, methodology and results of the study
- results - folder with the latex files to generate analysisplan_results.pdf
- memos.pdf - researcher notes on issues and decision making during the analysis
- definitions_audit.pdf - definitions of higher level themes included in the results report
- codes_audit.pdf - extended definitions file containing all the codes and themes
- conflicts_analysis_audit.nvpx - NVivo file with complete coding

Introducing paper: Interpersonal Conflicts During Code Review