Slashdot reader jb373 is a senior software engineer whose team’s bug-tracking methodology is making it hard to track bugs.
My team uses agile software methodologies, specifically scrum with a Kanban board, and adds all bugs we find to our Kanban board. Our Kanban board is digital and similar to Trello in many regards and we have a single list for bugs… We end up with duplicates and now have a long list to try and scroll through… Has anyone run into a similar situation or do things differently that work well for their team?
The original submission ends with one idea — “I’m thinking about pushing for a separate bug tracking system that we pull bugs from during refinement and create Kanban cards for.” But is there a better way? Leave your own experiences in the comments. How does your team track and manage bugs in your software?
Read more of this story at Slashdot.