The Programmer's Dilemma

Post by raganwald » Tue, Jun 07, 2011, 2:02 AM UTC

will_sargent wrote: post #50

raganwald wrote: post #49

Earlier quoted context omitted.

My claim is that if a project that uses Agile fails, the participants still have an incentive in dysfunctional cultures to blame each other, it's just that the structure of Agile makes it harder to blame individuals. So I am not claiming that A is better than W or W is better than A at shipping software, I am claiming that W is better than A at blaming people for failures. I might have confused the issue by trying to…

Can you explain how the structure of Agile makes it harder to blame individuals?

Post by will_sargent » Wed, Jun 15, 2011, 7:12 PM UTC

raganwald wrote: post #51

will_sargent wrote: post #50

Earlier quoted context omitted.

Can you explain how the structure of Agile makes it harder to blame individuals?

Perhaps we could pick a methodology and then imagine a project that "fails." Given this scenario, the challenge would be to find a way to blame the participants for the failure. What promises do developers and stakeholders make to each other in the methodology? How do you define "failure" and given that definition, how do you establish a causal relationship between an individual and the result?