Eric Sink has a great post about the realities of fixing bugs. Bottom line: every bug has both a benefit and a cost, and you’d best make sure that the benefit of fixing a bug outweighs the cost of doing so. Eric’s got lots more about how to derive the numbers to plug into that formula.
The Economics of Bug-fixing
Published In Archives
About This Article
Subscribe for more
Get stories like this in your inbox
Related content
Article
in Software
5 tips for shifting left in continuous testing
This is a guest post by Shani Shoham, President and COO for Testim.io, a test automation platform that uses machine learning to create self-healing stable tests. [cta]What is continuous testing? In broad terms, it means testing from the beginning to the end of each development cycle. It means running unit tests, functional tests, performance tests, […]
Article
in Software
Making it easier to track product bugs and suggestions
We love how you adapt our tools to suit the needs of your teams, and when you come across items to bring to our attention your feedback is invaluable. Specifically, to effectively prioritize bugs and suggestions, we’re moving several jira.atlassian.com (JAC) projects into new projects focused on the cloud and server. This change will apply […]
Article
in Inside Atlassian
Improving how we handle your feedback
At Atlassian, we’re always trying to improve how we operate, and dealing with issue reports from customers is no exception. We’ve noticed for a while that many of our customers struggle to find the right channel to report issues with Atlassian products, so recently we set out to fix this. In the past, there were […]