Every fantastic line of code you write has the potential to become an even more amazing bug — whether you report it or not, it’s there, lurking behind the scenes, but there.
As a Software Manager, it’s just not enough to look triage, monitor, and report on bugs (all very important), but what’s even more important is to identify if the bug is a bug or if it’s the tip of the iceberg of something that much bigger.
Whether its bugs being logged through your fancy dancy CI/CD pipelines or some schmancy CRM implementation that links them to incoming cases — it’s on you, the manager, to ensure you’re tracking not only what the impact today is but what the fall-out could be later down the line to ensure what’s a bug today doesn’t become debt tomorrow.
Watch the Trends
Identifying where bugs originate is the best place to analyze trends on where issues are coming from.
Don’t know where your bugs are originating from? GREAT — this is the best place to start to figure that out.
If over a two-week period we have 5 to 7 issues coming from our medium-sized customers on a particular area, you know when the bigger accounts get there, it’s not going to be a slow burn like it might have been with the medium ones and they probably aren’t going to be an issue.
