I certainly recommend mixing production in an iteration as a form of risk mitigation. If you have three reports to deliver this week and something goes haywire in the report framework, you won't be able to deliver anything. If you implement one report, one UI enhancement, and one performance improvement; then even if one blows up you're likely to be able to deliver the other two.
I still don't understand mixed production in lean manufacturing, but it makes sense in XP as a way to reduce risk. Kent Beck Three Rivers Institute > -----Original Message----- > From: Steven Gordon [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 09, 2004 7:18 AM > To: [EMAIL PROTECTED] > Subject: RE: Software Factories Considered Harmful (was RE: > [XP] Why NOT XP?) > > > > Have you read "Lean Software Development: An Agile Toolkit" by > Mary & Tom Poppendieck http://www.poppendieck.com/ld.htm ? > While I do not recall them discussing the specific issue of mixed > prodcution lines, they make a strong case about what does and does > not translated from Lean Manufacturing to software development, > and then derive some principles for Lean Software Development that > look amazing like the principles of Agile Software Development. 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/
