Skip to main content

Applying the ‘Wisdom of the crowd’ effect in software development

I’m currently reading Noise: A Flaw in Human Judgment, the latest book by Daniel Kahneman wo also wrote Thinking, Fast and Slow.

I’m only halfway in the book but in one chapter the authors talk about an experiment done by 2 researchers, Edward Vul and Harold Pashler where they gave a person a specific question not once but twice. The hypothesis was that the average of 2 answers was always closer to the truth than each answer independently.

And indeed they were right.

One knows more than one

Turns out that this is related to the wisdom-of-crowds-effect; if you take the average of a number of independent answers from different people it typically leads to a more correct answer.

I never heard about this effect before, but it turns out that I’m applying this principle for a long time based on something I discovered in the Righting Software book by Juval Löwy, the broadband estimation technique.

This technique allows you to estimate the implementation effort for a complex system in a fast and efficient way. The idea is that you bring a large group of people(diversity of the group is key!) together and ask them to estimate the effort to build this system.  By doing this with a large enough(think somewhere between 12 and 30 people) you are applying the wisdom-of-the-crowds effect to produce more accurate results.

UPDATE: I forgot to emphasize something when applying the wisdom-of-crowds-effect. It is really important that the estimations are done independently(!) of each other. If you allow people to align first, you end up with group-thinking and skewed estimations.

Important when applying this technique is that the outliers, values that were at least one standard deviation removed from the average, are not ignored but serve as a way to identify uncertainties. After the reasoning behind these outliers is explained a new estimation round is conducted. This process is repeated until all estimations fall within one standard deviation.

I had some very good results applying this technique but it was only when reading about the wisdom-of-crowds-effect that I started to understand the science behind it.

And now it is time to continue reading as I want to find out how I can further reduce the noise in our estimations…

More information

Noise: A Flaw in Human Judgment – Wikipedia

Wisdom of the crowd – Wikipedia

Righting Software | A Method for System and Project Design by Juval Löwy

Measuring the Crowd Within: Probabilistic Representations Within Individuals (ucsd.edu)

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         ...

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.

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...