My people aren’t participating

I frequently hear “my people won’t speak up during standup” or “they aren’t participating in retro” or other activities. Unfortunately, there are many different reasons why this might be so it’s not a simple problem to fix. Step one is to figure out why this might be happening.

Stalled work

As I talked about in this earlier video on standups, the work on our board can loosely be grouped into three categories. It’s either active, blocked, or stalled. We tend to spend a lot of time talking about the active and blocked work and have a tendency to forget about the rest, which results in stalled work aging unnecessarily. That in turn will make the overall system less effective and less predictable.

Warning levels

Over my career, I’ve noticed that a significant number of programmers ignore compiler and linter warnings. They either turn the warning levels down or just ignore the output. I’ve worked with teams using SonarQube that would have tens of thousands of warnings that they wouldn’t even look at.

“This is a safe space”

I’m seeing more and more situations where someone will say “this is a safe space” in a meeting invite or at the beginning of a session. While I appreciate that the person saying the words really wants that to be true, the fact they feel the need to say it, highlights the fact that it probably isn’t. If it really were safe, we would already know that.

Slicing epics

We talk a lot about slicing stories but then when it comes to slicing larger types (epics, features, etc), we tend to wave our hands and say “it’s the same, only bigger”, which while true, is rarely helpful.

Six Thinking Hats Retrospective

Six Thinking Hats is an approach for creativity that was created by Edward DeBono. I use it as the basis for an agile retrospective, and find this approach to be particularly effective when the topic we’re discussing is expected to be controversial or heated.

Remote work vs in-person: What does the data say?

When the worst effects of COVID had appeared to pass, many companies started implementing return-to-office mandates for their knowledge-workers, which have been controversial at best. The decision to do this was based on gut reactions from managers who, having no actual data, made the best guesses they could with what they knew.

Inattentional blindness

Inattentional blindness is when we are so focused on some things that we completely miss other things that should be completely obvious. This can be used to hilarious effect, as you’ll see below, and at the same time is something we need to take into account in business.

Linguistic Antipatterns

A linguistic antipattern is a place in the code where the naming implies that it does one thing and in fact, it does something different. For example, the method void isEmpty() suggests that it will return a boolean reflecting whether or not the object is empty, yet the method does not return anything.