Making software defect correction “fun” [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed last year.

Improve this question

Where I work we occasionally come across really challenging defects, which require a great deal of technical expertise, skill and patience to resolve. Getting our most talented engineers to work on these issues (especially on legacy code) can be quite challenging.

My question to the community is this: Have you successfully tried any techniques which would make such challenge support activities attractive/fun? If so, could you share what you have done?

Of course we could just pick the most talented engineers and instruct them to work on these issues, but forcing them to do this type of work on an ongoing basis can lead to dis-enfranchisement, which is not something we want.

Answer 1

Show me someone who cares. Fixing bugs from an unfeeling checklist gets to be a drag. If the fix will put a smile on someone’s face, let me see it.

Don’t make me work alone. Every bug fix is a chance to learn something and it is great fun to share something you learned with someone else.

Let me do more than just fix bugs. Sometimes bugs show you a better design just waiting to be uncovered. Don’t sell your team short. Let them do a little exploring.

Answer 2

Additionally, laud bug fixing.

It must be held in esteem by the business, and treated equivalently (if not superior) to delivering a feature. Otherwise why would I fix something when no one cares and also risk being rebuked for wasting time/resources/not delivering business value.