Skip to main content

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.

2
  • 5
    I like this answer the best. Not every bug is an emergency. Someone needs to prioritize bugs along with the customer so they know the trade-off: fix the bug or get a shiny new bike. Pushing the decision to the customer makes them aware of these issues. Once the distractions start affecting the bottom line, you'll get pressure to stabilize the product. This gives you leverage to slow down the release schedule so you can more thoroughly test things. Again, give the customer a choice: stabilize the product or accept monetary losses. Profit always seems to win. Commented Dec 20, 2023 at 21:02
  • 3
    One other alternative to consider with bugs not being an emergency: How many of them can wait a sprint? If your bugs can wait a couple of weeks, then you can plan them into the next sprint as normal, but high priority backlog items. Commented Dec 20, 2023 at 21:26