[Discuss] Agile software for a nacent project

[sethg at ropine.com (Seth Gordon)]

I would agree that a good process, in the hands of incompetent
management, will lead to bad results. I was an education major in a
previous life, and I saw how processes that sounded good when I
learned about them in my ed classes could be corrupted into yet
another form of ineffective paint-by-numbers teaching.

But the reverse is also true: well-intentioned people who use *bad*
processes (because they don?t know better) will *also* screw up.

I?d rather work in an environment with good people and a bad process
than vice versa, but I?d *much* rather have good people using good
processes.

(And to address the issue of design, nothing prevents the manager of
an agile group from saying ?ok, in this sprint, we will only design
feature X, and not worry about implementation just yet?. The group I?m
in now has a couple of ?design X? stories on the board for this
sprint.)