Re:AgileFall – When Waterfall Sneaks Back into Agile
by jrochkind1 on Wednesday September 18, 2019 @12:51PM
(#21007254)
I agree that it is not inherent to Agile. (I'm more suspicious of "scrum", but I'll believe you that it's not either).
Like I said, I've had GREAT experiences with agile practices, my _favorite_ workplaces have been using agile practices. Also terrible ones. Knowing that the terrible ones were "doing agile wrong" didn't make them less terrible.
I even said very explicitly "It turns into a process that is more like waterfall, but..." So I'm a bit perturbed by your response insisting that this is not inherent to agile. When I was pretty explicit in saying that too.
LOTS of companies _saying_ their doing agile result in misery, even worse than before they pretended to do agile. On the other hand, doing agile well can be wonderful. In order to figure out how to make more of the wonderful than the terrible, we have to get _beyond_ just pointing out that "the agile manifesto clearly states". Cause it's clearly stated that already, and it hasn't stopped the terrible.
Like I said, I've had GREAT experiences with agile practices, my _favorite_ workplaces have been using agile practices. Also terrible ones. Knowing that the terrible ones were "doing agile wrong" didn't make them less terrible.
I even said very explicitly "It turns into a process that is more like waterfall, but..." So I'm a bit perturbed by your response insisting that this is not inherent to agile. When I was pretty explicit in saying that too.
LOTS of companies _saying_ their doing agile result in misery, even worse than before they pretended to do agile. On the other hand, doing agile well can be wonderful. In order to figure out how to make more of the wonderful than the terrible, we have to get _beyond_ just pointing out that "the agile manifesto clearly states". Cause it's clearly stated that already, and it hasn't stopped the terrible.