@misc{Matthies2019,
  author    = {Matthies, Christoph},
  title     = {Agile process improvement in retrospectives},
  series = {41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)},
  journal   = {41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)},
  publisher = {IEEE},
  address   = {New York},
  isbn      = {978-1-7281-1764-5},
  issn      = {2574-1934},
  doi       = {10.1109/ICSE-Companion.2019.00063},
  pages     = {150 -- 152},
  year      = {2019},
  abstract  = {Working in iterations and repeatedly improving team workflows based on collected feedback is fundamental to agile software development processes. Scrum, the most popular agile method, provides dedicated retrospective meetings to reflect on the last development iteration and to decide on process improvement actions. However, agile methods do not prescribe how these improvement actions should be identified, managed or tracked in detail. The approaches to detect and remove problems in software development processes are therefore often based on intuition and prior experiences and perceptions of team members. Previous research in this area has focused on approaches to elicit a team's improvement opportunities as well as measurements regarding the work performed in an iteration, e.g. Scrum burn-down charts. Little research deals with the quality and nature of identified problems or how progress towards removing issues is measured. In this research, we investigate how agile development teams in the professional software industry organize their feedback and process improvement approaches. In particular, we focus on the structure and content of improvement and reflection meetings, i.e. retrospectives, and their outcomes. Researching how the vital mechanism of process improvement is implemented in practice in modern software development leads to a more complete picture of agile process improvement.},
  language  = {en}
}
@misc{Matthies2019,
  author    = {Matthies, Christoph},
  title     = {Feedback in Scrum},
  series = {2019 IEEE/ACM 41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)},
  journal   = {2019 IEEE/ACM 41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)},
  publisher = {IEEE},
  address   = {New York},
  isbn      = {978-1-7281-1764-5},
  issn      = {2574-1934},
  doi       = {10.1109/ICSE-Companion.2019.00081},
  pages     = {198 -- 201},
  year      = {2019},
  abstract  = {Improving the way that teams work together by reflecting and improving the executed process is at the heart of agile processes. The idea of iterative process improvement takes various forms in different agile development methodologies, e.g. Scrum Retrospectives. However, these methods do not prescribe how improvement steps should be conducted in detail. In this research we investigate how agile software teams can use their development data, such as commits or tickets, created during regular development activities, to drive and track process improvement steps. Our previous research focused on data-informed process improvement in the context of student teams, where controlled circumstances and deep domain knowledge allowed creation and usage of specific process measures. Encouraged by positive results in this area, we investigate the process improvement approaches employed in industry teams. Researching how the vital mechanism of process improvement is implemented and how development data is already being used in practice in modern software development leads to a more complete picture of agile process improvement. It is the first step in enabling a data-informed feedback and improvement process, tailored to a team's context and based on the development data of individual teams.},
  language  = {en}
}