Dan joins Vasco to talk about how we can communicate data when working with stakeholders and the team. He’s joined the podcast previously to talk about #NoEstimates with Vasco and Marcus Hammarberg. You can listen to that episode here.
We start the conversation by discussing some of the most common anti-patterns we fall into when communicating data to stakeholders and the team. The first anti-pattern Dan mentions is “assuming that people understand the data you present to them”.
We discuss why that is often a problem, and the role of rationality when discussing and deciding on what interventions are warranted based on the data that is presented.
In this segment, we also discuss that the role of data, and presenting data, is to assess what actions might be necessary to correct something, or improve the process we work with.
The emotions behind our reactions to the data being presented
As Marcus quickly found out in this project, the rate of progress could not have been predicted easily at the start (if at all). When he first started the project, the progress was swift, but at one point he faced a problem he could not solve for several days. This phenomenon is not new for any programmers in the audience, and is quite common. Also, one of the reasons why using methods like #NoEstimates (as explained in the #NoEstimates book, and in Marcus’ blog post), can help uncover information that estimation would not.
Dealing with surprises: the information you need to share with stakeholders