Comments on: Review: Ko's An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks http://blog.webfoot.com/2006/12/15/programmer-productivity-part-2/ Wed, 18 Nov 2009 14:52:27 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Best Webfoot Forward » VanDev talk summary http://blog.webfoot.com/2006/12/15/programmer-productivity-part-2/comment-page-1/#comment-199 Best Webfoot Forward » VanDev talk summary Thu, 07 Feb 2008 05:29:42 +0000 http://www.webfoot.com/blog/2006/12/15/programmer-productivity-part-2/#comment-199 [...] I have reported previously on experiments by Demarco and Lister, Dickey, Sachman, Curtis, and Ko which measure the time for a number of programmers to do a task. What I found is that the time [...] [...] I have reported previously on experiments by Demarco and Lister, Dickey, Sachman, Curtis, and Ko which measure the time for a number of programmers to do a task. What I found is that the time [...]

]]> By: Best Webfoot Forward » Review: Dickey on Sackman (via Bowden) http://blog.webfoot.com/2006/12/15/programmer-productivity-part-2/comment-page-1/#comment-198 Best Webfoot Forward » Review: Dickey on Sackman (via Bowden) Fri, 15 Jun 2007 00:22:13 +0000 http://www.webfoot.com/blog/2006/12/15/programmer-productivity-part-2/#comment-198 [...] small sample size hurts, but (as in the Curtis data and the Ko data) I don’t see an order of magnitude difference in completion [...] [...] small sample size hurts, but (as in the Curtis data and the Ko data) I don’t see an order of magnitude difference in completion [...]

]]> By: gpoo http://blog.webfoot.com/2006/12/15/programmer-productivity-part-2/comment-page-1/#comment-197 gpoo Wed, 16 May 2007 03:00:29 +0000 http://www.webfoot.com/blog/2006/12/15/programmer-productivity-part-2/#comment-197 The table it seems wrong. The values you had taken belongs to table 3, page 975 of the paper. However, the average time for scroll was 17 minutes. 64.5 was the average of actions for that activity. Moreover, 70 minutes was given to each developer to do 5 tasks. So, having 64 minutes as average means they had only 6 minutes for the rest of the tasks which is contradictory according the rest of the table. The same happens with the standar deviation. +/- 13 minutes instead of +/- 55 minutes. Regards, The table it seems wrong.

The values you had taken belongs to table 3, page 975 of the paper. However, the average time for scroll was 17 minutes. 64.5 was the average of actions for that activity.

Moreover, 70 minutes was given to each developer to do 5 tasks. So, having 64 minutes as average means they had only 6 minutes for the rest of the tasks which is contradictory according the rest of the table.

The same happens with the standar deviation. +/- 13 minutes instead of +/- 55 minutes.

Regards,

]]> By: Best Webfoot Forward » Programmer productivity — part 3 http://blog.webfoot.com/2006/12/15/programmer-productivity-part-2/comment-page-1/#comment-196 Best Webfoot Forward » Programmer productivity — part 3 Fri, 16 Feb 2007 03:06:37 +0000 http://www.webfoot.com/blog/2006/12/15/programmer-productivity-part-2/#comment-196 [...] My recent reflections on the Curtis results and reflections on the Ko et al results of experiments of programmer productivity have focused on one narrow slice, what I call “hands-on-keyboard”. Hands-on-keyboard productivity is measured by how fast someone who is given a small, well-defined task can do that task. As I mentioned in those two blog posts, it is hard to measure even that simple thing. [...] [...] My recent reflections on the Curtis results and reflections on the Ko et al results of experiments of programmer productivity have focused on one narrow slice, what I call “hands-on-keyboard”. Hands-on-keyboard productivity is measured by how fast someone who is given a small, well-defined task can do that task. As I mentioned in those two blog posts, it is hard to measure even that simple thing. [...]

]]>