Comments on: Cup of Coffee Metric for Continuous Integration http://pauljulius.com/blog/2009/09/14/cup-of-coffee-metric-for-continuous-integration/ Paul Julius's web log. Sat, 06 Feb 2010 04:14:02 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Pinoy Sikat http://pauljulius.com/blog/2009/09/14/cup-of-coffee-metric-for-continuous-integration/comment-page-1/#comment-482 Pinoy Sikat Sat, 06 Feb 2010 04:14:02 +0000 http://pauljulius.com/blog/?p=59#comment-482 Our community needs this kind of advices. Keep it up!. Our community needs this kind of advices. Keep it up!.

]]> By: Jeffrey Fredrick http://pauljulius.com/blog/2009/09/14/cup-of-coffee-metric-for-continuous-integration/comment-page-1/#comment-410 Jeffrey Fredrick Tue, 15 Sep 2009 15:03:34 +0000 http://pauljulius.com/blog/?p=59#comment-410 Hi Curtis, the book you're talking about came out in 2007. I started talking about the "cup-of-coffee" rule back in 2004 (though oddly not blogging about it, so I'm happy Paul did). I think the advantage of the fuzzy coffee rule is that when you give it with a story it helps people understand why it is important — avoiding the cost of context switching — in a way that "5 minutes" or "10 minutes" don't convey. Sure, a fixed time is more actionable, and I'm all in favor of that too, but I think the story around coffee/tea is more memorable. (Example of the story in <a href="http://www.stickyminds.com/BetterSoftware/magazine.asp?fn=cifea&id=58" rel="nofollow">this article</a>.) Jtf Hi Curtis,

the book you’re talking about came out in 2007. I started talking about the “cup-of-coffee” rule back in 2004 (though oddly not blogging about it, so I’m happy Paul did).

I think the advantage of the fuzzy coffee rule is that when you give it with a story it helps people understand why it is important — avoiding the cost of context switching — in a way that “5 minutes” or “10 minutes” don’t convey. Sure, a fixed time is more actionable, and I’m all in favor of that too, but I think the story around coffee/tea is more memorable.

(Example of the story in this article.)

Jtf

]]> By: Curits http://pauljulius.com/blog/2009/09/14/cup-of-coffee-metric-for-continuous-integration/comment-page-1/#comment-409 Curits Tue, 15 Sep 2009 12:27:56 +0000 http://pauljulius.com/blog/?p=59#comment-409 I think it was Glover and Duvall and guys at his old firm (Stelligent?) that started the 10-minute rule (Didn't you contribute a foreward to this book too?). Build need to finish and report in <10minutes, your cup-of-coffee but with real numbers. Through modularization of our build process we have consistently been hitting this metric. f course we are only compiling, packaging and running the Unit Test but that should be enough. Immediately after that,, after the buld success or failure notification went out, we go on to run our longer running, more comprehensive build complete with code scans, Site and Sonar reports. So, like 'technical debt' while cute and fun to talk about I feel Coffee Metric is a little too fuzzy for people to apply. I'm sticking with 10 minutes and let them decide what to do with their time ;-) I think it was Glover and Duvall and guys at his old firm (Stelligent?) that started the 10-minute rule (Didn’t you contribute a foreward to this book too?). Build need to finish and report in <10minutes, your cup-of-coffee but with real numbers. Through modularization of our build process we have consistently been hitting this metric. f course we are only compiling, packaging and running the Unit Test but that should be enough. Immediately after that,, after the buld success or failure notification went out, we go on to run our longer running, more comprehensive build complete with code scans, Site and Sonar reports.

So, like 'technical debt' while cute and fun to talk about I feel Coffee Metric is a little too fuzzy for people to apply. I'm sticking with 10 minutes and let them decide what to do with their time ;-)

]]>