Software. It’s buggy. Always. Even when you did everything in your power to keep the bugs out. As soon as real people start using it, the bugs come out of the codewood, so to speak.
It’s not whether your code is bug-free but how you deal with bugs that counts. The more efficiently you squash them and learn from them the better.
Here are five tips for managing software incidents.
- Collect data. Yes you want to get the bug fixed, but you want to learn from it, too. And yes, all the data will likely be there later, but collecting things like relevant sections of logs and screenshots while it’s happening is going to make it much easier to do a post-mortem.
- Fix the bug. I mean, this may seem obvious but don’t lose the forest for the trees. And don’t, as some companies do–not yours, of course, but some companies do–let the problem linger in the “to be fixed” list until it becomes a security risk and you don’t have time to properly document it.
- Investigate as soon as it’s over. Once you’ve fixed it, have a developer take charge while everything is still fresh. Collect all that data you preserved and get the info recorded from everyone involved, so it’s clear what happened.
- Review quickly. Once you’ve organized all the info, don’t wait. Within a week bring together everyone impacted by it and do 30 minutes or so on what happened and what you can do in the future to make sure it doesn’t happen again.
- Share what you learned. Don’t hide that report away. Make it available where everyone in the company can access it and learn from it even if they weren’t impacted.
Yes you will have bugs, but hopefully the big ones will be few and far between, and you’ll get faster and better at dealing with them.
Subscribe to TechRepublic Top 5 on YouTube for all the latest tech advice for business pros from Tom Merritt.
Subscribe to the Developer Insider Newsletter
From the hottest programming languages to commentary on the Linux OS, get the developer and open source news and tips you need to know. Delivered Tuesdays and Thursdays