tag:blogger.com,1999:blog-23992350.post3630035013664165705..comments2008-08-12T15:02:59.107+01:00Robbiehttp://www.blogger.com/profile/08233833428126146585noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-23992350.post-60623341437770134282008-08-12T15:02:00.000+01:002008-08-12T15:02:00.000+01:00the way i use code metrics is to flag up issues when i am coding: as means of getting immediate feedback from the IDE to act and correct immediately. I don't think of code metrics as means to police code or measure ultimate quality. Pairing and code reviews are more appropriate in that respect.<BR/><BR/>as for enterprise and agile i found this blog - you may be interested http://scalingsoftwareagility.wordpress.com/2008/08/11/revised-big-picture-graphic-and-posts-1-4/smartricshttp://www.blogger.com/profile/07295654362099098666noreply@blogger.comtag:blogger.com,1999:blog-23992350.post-17238558750894010862008-08-08T11:14:00.000+01:002008-08-08T11:14:00.000+01:00Really reckon that the main difference between startup agile and the enterprise sort it that the enterprise encourages all sorts of metrics, sometimes over delivery. whereas a start up just says "when can i launch it"?<BR/><BR/>Both will change there mind during delivery cycles, and it's flexibility to me that is the key part of agility, as opposed to "god we can measure all this stuff"<BR/><BR/>code quality is a factor of code size, and the larger and more complex the code base, the higher the level of quality required. start up code starts small, and sometimes suffers from not increasing quality as the size of code base grows.Tim Stevenshttp://www.blogger.com/profile/05946371696574191455noreply@blogger.com