Are Our Decisions in Agile Free of Cognitive Biases?

"I knew this release was bound to fail. We shouldn't have hurried." If you ever heard a Scrum Master mentioning this, he/she could be under the influence of a "hindsight bias." Another scenario is when an Agile team agrees blindly with a confident-sounding (and looking) Product Owner without empirical evidence, they may be subject to the "halo effect." Or, when a tester in good mood agrees to execute 40% higher test cases than their previous average, the tester may be experiencing "optimism bias."

I know, some of you could now be thinking: "That is what Agile is all about. We need to try out and experiment. It could be wrong, but learn lessons from it."  Agreed! But what about understanding the scientific reason for flawed decision-making, which if addressed appropriately, could minimize some of these errors? I am referring here to a psychological phenomenon called "cognitive Bias."

Don’t Be Quick to Judge Your Team Members

Judging others infographic.

Think of the countless times you labeled someone at work as "lazy, boring, incompetent, stupid, irritating, biased, reckless, rude, etc."

The lens with which you see others makes all the difference; are you quick to judge or adopt an attitude to understand?

How your co-worker reacts to a situation is shaped by their own temperament, past experiences, and current circumstances. Their behavior in one area does not reflect who they are as a person, what they value, and even how they would be in another aspect of their work.