| You can try your best but bugs seem to me to be a necessary tradeof for “getting stuff out there”. Some are generally acceptable given that the applications we write these days generally aren’t for life threatening devices etc. What I’d do in your situation is bring these issues up with the team and think of what if anything you can do to help reduce the amount of support tickets coming through. I’d look at reoccurring support tasks and prioritise the proper fixing of these based on the frequency these tasks come up. I’d raise specific bugs that have come about recently and ask if you as a team could have prevented these in any way. What lessons do these have for the future? Maybe you can get a “story sign off” from the product owner once tasks are done you demonstrate that the feature works as expected. Another thought is to write up more formal acceptance criteria with various scenarios in story cards “As a, I would like, so that”, “Given When Then” kinda stuff. Might need to google on that one. Anyway, I think if you take the actions you can take and maybe reframe the way you think of bugs, you can rest a bit easier. Just remember it’s a team effort, and hopefully your team members can help pitch in to help solve these with you. |