tag:blogger.com,1999:blog-736810000699453506.post3018409396038079149..comments2023-05-11T00:49:36.314-07:00Comments on Ruminations on Computing: Making Hard Choices - Which Bugs Do We Fix?Steve Rowehttp://www.blogger.com/profile/17905356014908630180noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-736810000699453506.post-69268150795582225122006-06-13T12:25:00.000-07:002006-06-13T12:25:00.000-07:00Risk levels are not static through the development...Risk levels are not static through the development cycle.<br><br><br>For example, the closer the product gets to being released, the risk for fixing any bug increases.Greg Miskinnoreply@blogger.comtag:blogger.com,1999:blog-736810000699453506.post-62054226590089450892006-06-13T18:29:38.000-07:002006-06-13T18:29:38.000-07:00You are correct. Risk levels are not static. Ear...You are correct. Risk levels are not static. Early in a project, all fixes are on the table. Everything that is found gets fixed or at least gets on the list of things to be fixed. If something goes wrong, there is plenty of time to correct it later. As the project nears completion, however, the risk rises and so does the bar for fixing bugs. A "one line fix" might be rejected if it is late enough in the project. While it might seem innocuous, there could be consequences. If everything goes right, it is a no-brainer but it might somehow change the program flow or it could inadvertendly break the build costing everyone critical time.SteveRowenoreply@blogger.com