Table of Contents
Fetching ...

Exploring Retrospective Meeting Practices and the Use of Data in Agile Teams

Alessandra Maciel Paz Milani, Margaret-Anne Storey, Vivek Katial, Lauren Peate

TL;DR

The paper investigates how Agile teams incorporate objective project data into retrospective meetings, addressing a gap where subjective reflections dominate. Through a survey of 19 teams conducted with an industry partner, it shows that data-driven practices are rarely systemic, with barriers including psychological safety and weak integration into existing processes. It offers actionable insights to ease access to diverse data, encourage pre-session data discussion, and foster a balance between humane, reflective dialogue and data-informed decision making. The study contributes to improving retrospectives by outlining practical interventions and guiding future research toward harmonizing human-centric reflection with objective project data for better software process improvements.

Abstract

Retrospectives are vital for software development teams to continuously enhance their processes and teamwork. Despite the increasing availability of objective data generated throughout the project and software development processes, many teams do not fully utilize this information in retrospective meetings. Instead, they often rely on subjective data, anecdotal insights and their memory. While some literature underscores the value of data-driven retrospectives, little attention has been given to the role data can play and the challenges of effectively incorporating objective project data into these meetings. To address this gap, we conducted a survey with 19 practitioners on retrospective meeting practices and how their teams gather and use subjective and objective data in their retrospectives. Our findings confirm that although teams routinely collect project data, they seldom employ it systematically during retrospectives. Furthermore, this study provides insights into retrospective practices by exploring barriers to project data utilization, including psychological safety concerns and the disconnect between data collection and meaningful integration of data into retrospective meetings. We close by considering preliminary insights that may help to mitigate these concerns and how future research might build on our paper findings to support the integration of project data into retrospective meetings, fostering a balance between human-centric reflections and data-driven insights.

Exploring Retrospective Meeting Practices and the Use of Data in Agile Teams

TL;DR

The paper investigates how Agile teams incorporate objective project data into retrospective meetings, addressing a gap where subjective reflections dominate. Through a survey of 19 teams conducted with an industry partner, it shows that data-driven practices are rarely systemic, with barriers including psychological safety and weak integration into existing processes. It offers actionable insights to ease access to diverse data, encourage pre-session data discussion, and foster a balance between humane, reflective dialogue and data-informed decision making. The study contributes to improving retrospectives by outlining practical interventions and guiding future research toward harmonizing human-centric reflection with objective project data for better software process improvements.

Abstract

Retrospectives are vital for software development teams to continuously enhance their processes and teamwork. Despite the increasing availability of objective data generated throughout the project and software development processes, many teams do not fully utilize this information in retrospective meetings. Instead, they often rely on subjective data, anecdotal insights and their memory. While some literature underscores the value of data-driven retrospectives, little attention has been given to the role data can play and the challenges of effectively incorporating objective project data into these meetings. To address this gap, we conducted a survey with 19 practitioners on retrospective meeting practices and how their teams gather and use subjective and objective data in their retrospectives. Our findings confirm that although teams routinely collect project data, they seldom employ it systematically during retrospectives. Furthermore, this study provides insights into retrospective practices by exploring barriers to project data utilization, including psychological safety concerns and the disconnect between data collection and meaningful integration of data into retrospective meetings. We close by considering preliminary insights that may help to mitigate these concerns and how future research might build on our paper findings to support the integration of project data into retrospective meetings, fostering a balance between human-centric reflections and data-driven insights.

Paper Structure

This paper contains 30 sections.