> Craig Larman's book does a great job of comparing XP
> by-the-book to other iterative processes. Forbidding
> up-front documentation, and forbidding design
> documentation, helps you go faster, but leaves no
> paper trail.
Which processes forbid design documentation and up-front
documentation? The only one I can think of is Semco's 10
year plan (which is never written down, although their
short term plan is). I'd be interested in learning how
these processes work.
If XP by-the-book forbids it, please forgive me. It's
been a long time since I read the book and I've
forgotten.
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
