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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more