written this on (or about) Fri, 20 Jun 2003 15:24:18 GMT, :
"Phlip" <phlipcpp@yahoo.com> wrote in messagenews:RiEIa.2623$Ul7.2295@newssvr31.news.prodigy.com... (A typical XP iteration is 2 weeks, but I suggested 1 week iterations because when a team is in trouble - such as when they have a fretful customer - they must become >more< extreme, not less.)So, 2 weeks is extreme, 3 weeks is less extreme, and 1 week is more extreme?Hey, if being extreme is good, why not make the iterations be 2 seconds?Would that be "way more" extreme?
Interestingly enough, the code for the computer in the Mercury space
capsule was developed using iterations of four *hours*. And tests
were written before code. (According to Craig Larman's wonderful
history of iterative development paper in IEEE)
I often use four hour iterations when teaching XP or TDD in courses.
Amazingly enough, it works pretty well. Even so, I prefer one-two
week iterations.
Robert C. Martin | "Uncle Bob"
Object Mentor Inc.| unclebob @ objectmentor . com
PO Box 5757 | Tel: (800) 338-6716
565 Lakeview Pkwy | Fax: (847) 573-1658 | www.objectmentor.com
Suite 135 | | www.XProgramming.com
Vernon Hills, IL, | Training and Mentoring | www.junit.org
60061 | OO, XP, Java, C++, Python |