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.

Popular posts from this blog

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B