Re: [AM] Unfounded assertion

On Friday, January 30, 2004, at 08:41  pm, Randy Miller wrote:
[snip]
> Some activities, like code reviews, are
> clearly preventative. They keep people from making mistakes. Other
> activities, like requirements gathering, help people build the right
> system. Or maybe they prevent people from building the wrong system. I
> found it interesting to look at an activity as a guidance mechanism
> (with an enabling side and a prevention side) instead of something to
> hold you down or prop you up. Your message provoke that line of 
> thought.
[snip]

Interesting point of view. Of course a lot depends on how the activity 
is done.

The better code review sessions I've been involved were more about 
building the right system than they were about preventing mistakes. 
More "We can refactor that out into a new class" than "That will die 
horribly on edge case foo".

I'm sure I'm not alone in having the experience of a large requirements 
gathering process helping build the wrong system :-)

It's interesting that agile practices like TDD and pair programming 
turn find-the-defect activities into drive-the-design activities by 
tightening the feedback loop much as possible.

Adrian

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------