Running Code and Regular Releases
1a) Releasing a protoype when only 20% of the functionality is complete, was a significant predictor of both reduced defect-rate and increased productivity.
1b) Both formal design reviews and regression tests were significant predictors of reduced defect-rate (but not productivity).
1c) Daily builds were a significant predictor of increased productivity (but not reduced defect-rate).
1d) There was no significant association between either defect-rate or productivity, and dividing a project into subcycles (which developed a subset of the final functionality).
Conclusion: Get a prototype into the hands of customers asap.
http://www.cc.gatech.edu/classes/AY2005/cs6300_fall/papers/maccormack
2a) One-third of the variation in product quality was explained by how quickly customers were given the first beta version.
2b) The data showed no relationship between the final product quality and the number of beta releases.
Conclusion: “Get a low-functionality version of the product into customers’ hands at the earliest possible stage…”
http://www.sloanreview.mit.edu/smr/issue/2001/winter/6/
Posted by: Isaac Gouy at February 11, 2005 11:59 AM