Pitfalls to avoid during the software development process.

This revisited post presents my?checklist of ??pitfalls to avoid?? during the software development process.

I am aware that some of the items are overlapping, disputable and that the list itself is not exhaustive. However, it has worked for me in many cases, and I am certain that at least some?of the items will be extremely useful for you.

- Are we learning to do best what we should not be doing at all??

Implementing a continuous improvement process aligned with Lean Management principles is crucial for eliminating waste. Using value stream mapping can serve as a valuable starting point

- Consider how cognitive biases effect your decisions making

In general, cognitive bias refers to the systematic tendencies of the human brain to deviate from rationality or optimal judgment in decision-making processes. These biases arise from the brain's inclination to simplify complex information processing and can manifest in various forms, influencing perception, memory, and decision-making.

I consider the following cognitive biases as source of bad effect on our activities:

-??Status quo bias

-??Confirmation bias

-??Illusions of validity and skill

Referring to the publications of Robert Cialdini, Richard Thaler, and Daniel Kahneman is a good starting point to avoid the pitfalls of the cognitive bias.??

also see - Optimizing Software Development with Evidence-Based Approaches.

- Be clear: what is the problem we are trying to solve?

Albert Einstein quoted to say “If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions”.

The importance of being clear of what problem we are trying to solve was also mentioned by Stroustrup (the “father” of C++): “The most important single aspect of software development is to be clear about what you are trying to build.”

Just as a concrete example that might be immediately applied: remember all those endless meetings that are 80% waste of time. Being clear before the meeting as to what problem you are trying to solve will save all the participants a lot of time and frustration.???????

- Design and programming are human activities; forget that and all is lost -?Bjarne Stroustrup.

Do not overlook the huge importance of social intelligence and human capital. A good starting point is chapter 4 of Mastery by Robert Green - See People As They Are- Social Intelligence.

- To a man with a hammer, everything looks like a nail - Abraham Maslow

"To a man with a hammer, everything looks like a nail" is often referred to as the law of the instrument or the principle of the golden hammer.

It suggests that people tend to apply familiar tools or methods to solve problems, even when those tools may not be the most appropriate or effective for the situation at hand. In other words, it highlights the tendency to rely on a single approach or solution, regardless of whether it's the best fit for the problem. This concept encourages individuals to consider a range of options and approaches when addressing challenges, rather than defaulting to what is most familiar or comfortable.

My recommendation -Always focus on and pay attention to the problem you are trying to solve and avoid focusing on the tool.

Similar idea was mentioned by uncle bob:

- Cut the chase - avoid the bike-shed effect

The law of triviality, also known as "example of the bicycle shed", is a claim extracted from the book "Parkinson's Law" - discussions on important topics will end quickly while discussions on simple, trivial topics can take a long time.

The reason for this, is that many people do not understand complex issues, and therefore tend to make decisions about them without discussing the details. On the other hand, simple topics (and therefore, usually, of less importance) raise a discussion in which each of the participants can ostensibly prove his capabilities, and as a result extend the discussion to a great extent.

So – for your future meeting - avoid the bike-shed effect and cut the chase !

Feedback

Any feedbacks or question are mostly welcome.

Email:[email protected]

Mendelson Amir, Paris FRANCE