Is a bug in the code necessarily a bug in the process?

(pasted from agile forum)
>As Jim Shore says in his forthcoming book, a bug found in released code is
not only a bug in the code, but a bug in the development process. What
caused this bug to be produced? What caused it to not be caught prior to
release? How can we prevent this error in the future. The causes may be
anywhere from a coding error to a product concept that's not clear.

In traditional models of testing, I rarely see any credence given to the
idea that we can (even hope to) know everything before we start. This is
one of the reasons that I like agile--and sometimes Agile--processes, and
it's a reason why I'm enjoying "Artful Making" (Austin). I'd argue that a
bug is not necessarily linked to a bug in the development process if we
learn something from it. Austin goes so far as to say that it's not
necessarily a problem if we fail in the same way ten times, because we might
need ten iterations before we can get insight into what the problem really
is.

---Michael B.