tag:blogger.com,1999:blog-381129527146258002.post4410187870274539626..comments2024-03-28T00:17:26.580-07:00Comments on Agile Otter Blog: Heatmap: The new hotnessAgileotterhttp://www.blogger.com/profile/10773578598860454277noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-381129527146258002.post-25830862281018108302023-11-29T00:00:36.363-08:002023-11-29T00:00:36.363-08:00Interesting read! I love how you tackled the chall...Interesting read! I love how you tackled the challenge of bug prevention and used a practical approach with Jira and git commits. The heat map idea is genius—it provides a clear visual of where attention is needed. Jira time tracking can indeed play a crucial role in identifying patterns and areas for improvement. Looking forward to more insights from your data-driven approach!Flowacehttps://www.blogger.com/profile/14623760213434720534noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-80214966752408471402011-12-21T11:17:41.345-08:002011-12-21T11:17:41.345-08:00We have a heat map built into our jenkins build no...We have a heat map built into our jenkins build now at a client site. It is not a proper word cloud (would that be cool?) but instead is html. It sizes the files by the total number of changes, and colors it by the % of changes that are defects. <br /><br />We changed the script to be a 60-day sampling period. In the past two months, I can tell you where our activity has been and how much of the work was defects, and at a glance I know which files need to be REALLY clean.<br /><br />The visualization came from Brandon Carlson, including the idea of hovering on the name to see the path, total changes, and total defects. <br /><br />It's pretty sweet, really.Agileotterhttps://www.blogger.com/profile/10773578598860454277noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-68327725689889630612011-03-05T05:08:00.728-08:002011-03-05T05:08:00.728-08:00Great idea Tim. In my google tech talk http://bit....Great idea Tim. In my google tech talk http://bit.ly/80-20-rules I talk a lot about bug clusters. I mentioned using check out records as a guide for programs that need maintenance, but this extends that idea significantly by adding the "bugs found" weighting to the heat map. Great stuff!Erik Petersenhttps://www.blogger.com/profile/15533063091357812675noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-37991149565396014832010-12-07T12:21:27.984-08:002010-12-07T12:21:27.984-08:00Tim, you inspired a colleague and I. I've set ...Tim, you inspired a colleague and I. I've set up a project at https://github.com/andrewheald/code-heatmap to implement your ideas. Early days yet. It's taking shape. I'll post again when some solid results are coming of it.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-66318074168985707752010-10-13T13:49:15.778-07:002010-10-13T13:49:15.778-07:00Nice simple idea. It would be interesting (at leas...Nice simple idea. It would be interesting (at least to me) if the factor for defect related check ins actually makes much of a difference. <br /><br />Just guessing I would assume, new or newly changed code cause more trouble then old code.<br /><br />If this is true you should get more or less the same heatmap (at least for the hottest files) more or less independently of the weighting factor.Jens Schauderhttp://blog.schauderhaft.denoreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-36230215602646780282010-10-13T10:13:56.437-07:002010-10-13T10:13:56.437-07:00Now that it's a little later and we're abl...Now that it's a little later and we're able to act on it, the heat index is is proving to be a mighty good "bird dog."<br /><br />It is almost as if there is a correlation between ugliness of code and defects . I think maybe the takeaway is this:<br /><br />Ugly code touched often breaks often. <br /><br />I'll try to punctuate that later.Agileotterhttps://www.blogger.com/profile/10773578598860454277noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-83797358618014777432010-10-11T10:58:23.413-07:002010-10-11T10:58:23.413-07:00Brilliant, Tim. I like how that gets Management an...Brilliant, Tim. I like how that gets Management and Engineering on the same team.<br /><br />Don't get too granular with it though. Breaking it down file by file is universal in more than one way. It's language neutral, all managers understand what files are, and every version control system understands files.<br /><br />If people want to further develop the idea then they should be getting statisticians involved. They can help us develop those creepy smart algorithms for classifying files and improving our decisions.<br /><br />Anyway, completely brilliant. You and whoever else built that should be consuming Guinness and yelling a lot. For like 2 weeks at least.Darrin Thompsonhttps://www.blogger.com/profile/04037462028265507114noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-9457919486816182022010-10-09T04:28:22.736-07:002010-10-09T04:28:22.736-07:00The code was written for my employer, and belongs ...The code was written for my employer, and belongs to the company. I really should get into some open source projects so that I can show my work. It is not available, but could be reproduced.<br /><br />It is fairly trivial once you know what you want. I spent most of my time figuring out what data I want and how I wanted to index it, what was meaningful, etc. <br /><br />You have enough of a head start here that you could almost certainly reproduce the results using the tools for your project.<br /><br />I considered digging data out of code, but am pleased that instead I used the historical record without looking into code. We parsed our simian report (similarity index) and originally were adding duplication into the heat map, but then decided that a purely historical record was more credible than one with code theory.<br /><br />What I would like to incorporate in the future is code coverage, but we would have to build up a record of the code coverage at each release and we don't have that currently. It should be a matter of checking out the code, running unit and fitnesse tests, and parsing the records. Coverage % would reduce the heat index and show us which files need work instead of just showing us which need to be clean.<br /><br />I like your marker idea, and think it would be an interesting additional criteria to look at along with coverage.Agileotterhttps://www.blogger.com/profile/10773578598860454277noreply@blogger.comtag:blogger.com,1999:blog-381129527146258002.post-27179783616283290462010-10-09T03:42:00.673-07:002010-10-09T03:42:00.673-07:00Sounds like a great idea. Is there a public versio...Sounds like a great idea. Is there a public version of this heatmap collector? I'd also throw in the counting of task annotations in a file (@todo, @fixme, etc) that may refer to technical debt. The more there are in a file, the bigger attention is needed.mezahttp://alternateillusion.comnoreply@blogger.com