Skip to main content

Improve your Daily Scrum meetings

Normally when you are doing  Scrum, you have a Daily Scrum meeting. The idea is that you have a daily meeting where you basically determine how the work is progressing and if divine intervention is required to keep things progressing.

The goal is to provide a transparency where anyone can see what exactly the team is up to.

The basic format of a scrum meeting is pretty simple. Each person on the team says three things:

  1. What did I do since our last meeting
  2. What am I doing until our next meeting
  3. What is impeding me

Last week I was reading this post by John Sonmez about how these questions are too vague and can easily evolve to the following conversion:

“I continued to work on backlog X, I’ll continue to work on backlog X today.”

This is of course not very useful and a pure waste of time. I noticed that our own Scrum meetings were also evolving in this direction, so I took John Sonmez advice and tried replacing the 3 topics in a Scrum report with these:

  1. What did I commit to doing yesterday and did I or did I not meet that commitment. If not, why not.
  2. What will I commit to getting done today.
  3. What is impeding me that can be improved by bringing it up in this meeting.

This immediately changes the whole conversation and forces us to commit every day over and over again AND be truthful to ourselves realizing that we sometimes didn’t succeed in fulfilling these commitments.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more