I don't recall ever using the word "forbid". I have noticed that, all other things being equal, projects that communicate through code, tests, and social interaction run more smoothly than projects that rely on lots of other forms of documentation. Based on this observation, I recommend to teams that want to improve that they look at ways of eliminating redundant, non-value-adding documentation. This advice is entirely consistent with what I know about life-critical software development (which is all second hand).
Kent Beck Three Rivers Institute > -----Original Message----- > From: Phlip [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 6:46 AM > To: [EMAIL PROTECTED] > Subject: Re: [XP] new in XP > > 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. 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/
