In my experience:

Clustering happens when work gets interrupted. Say someone is shifted off the project so his work isn't fully tested, or maybe even completed, and/or the results not fully understood.

Clustering also happens because of the "bad programmer" problem. Say 5 people worked on something and one of them was sub-standard. The bugs will be associated with his work.

In my experience:

Clustering happens when work gets interrupted. Say someone is shifted off the project so his work isn't fully tested, or maybe even completed, and/or the results not fully understood.

Clustering also happens because of the "bad programmer" problem. Say 5 people worked on something and one of them was sub-standard. The bugs will be associated with his work.

The Pareto Principle applies (aka the 80/20 rule). Roughly 80% of the effects come from 20% of the causes. https://en.wikipedia.org/wiki/Pareto_principle Note this observation dates back from before computers.

In my experience:

Clustering happens work gets interrupted. Say someone is shifted off the project so his work isn't fully tested, or maybe even completed, and/or the results not fully understood.

Clustering also happens because of the "bad programmer" problem. Say 5 people worked on something and one of them was sub-standard. The bugs will be associated with his work.

In my experience:

Clustering happens when work gets interrupted. Say someone is shifted off the project so his work isn't fully tested, or maybe even completed, and/or the results not fully understood.

Clustering also happens because of the "bad programmer" problem. Say 5 people worked on something and one of them was sub-standard. The bugs will be associated with his work.