The quality of the software is a responsibility of the entire team. The Product Owner is responsible for building the right thing. Ensuring we build the thing right is the main responsibility of the development team. Scrum Masters serve a key role in achieving both aspects. A Scrum Master serves the team by coaching members in self-management and cross-functionality, helping them focus on creating high-value increments, and removing impediments. Sounds great, and abstract, so let us dive in with some practical examples. 

Discovering and interpreting beliefs in groups Ever been part of a conversation that seemed to revolve around the same issue over and over again? Or a meeting where some people keep diving into details and others want to stay more high-level? As consultants, we often come across these kinds of sessions. We noticed that these situations can lead to tension, slowing down and (healthy) conflict. Over time, we learned how to tackle these situations by using sensemaking, a technique that offers us the right insights to guide a workshop or decision-making.

KPIs, OKRs, SLIs, SLOs. Just a few metrics that potentially can be used within an organization. In recent years, an increasing emphasis has been placed on measuring and monitoring results. An understandable movement and one I wholeheartedly support. Often, I am helping organizations to become more aware of the impact they create by measuring the impact of their actions. Does it mean that metrics are simply great? Well not necessarily. Metrics have dysfunctional effects. Take for example the Cobra Effect.