Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    Do you want the team making the most bugs to "fix" those bugs or do you want the team that has a clue "fixing" the most bugs? Which approach do you think will result in a better system? Besides, frequently it might not be possible to know whose bug it is until the problem is found. Usually by that time, the fix is already identified and it would be quite inefficient to not just get it done right then and now just to reassign to another team. Also, there is no code ownership in agile. Commented May 13, 2014 at 14:50
  • 2
    Bugs detected post-development are a process smell. Why aren't these bugs being detected by the developers before release? Sounds like your testing is inadequate. If you work to improve pre-release testing life will get better. Commented May 13, 2014 at 15:40
  • 1
    @kevincline this goes without saying. But it's also obvious that some bugs will slip through the testing process. Commented May 13, 2014 at 22:08
  • 1
    Why can't you just re-assign the bug to the originating team? Commented May 14, 2014 at 1:30