"The average proportion of time spent actually fixing, rather than communicating a problem was 36%. Some 40% of technical support and application developers questioned spent less than 25% of their time fixing a problem. The remainder of their time was spent reproducing the problem on test systems and communicating it to other team members and people in the company, the survey found."

- Saran, C. (2004). Study finds poor communication is wasting developers' time. ComputerWeekly.com, Oct 26, 2004. Retrieved from http://www.computerweekly.com/articles/article.asp?liArticleID=134537&liArticleTypeID=1&liCategoryID=6&liChannelID=22&liFlavourID=1&sSearch=&nPage=1# on Oct 26, 2004.

Since when is "reproducing the problem on test systems" not part of "actually fixing" the problem? From this article, it seems like the statistics are flawed. Figuring out exactly how the bug behaves is one of the steps in determining how to fix the bug.

I am interested in how much time a development team really spends communicating, though.