Timeline for How to distribute development and bug fixes tasks
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2023 at 21:26 | comment | added | user1937198 | 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. | |
| Dec 20, 2023 at 21:02 | comment | added | Greg Burghardt | 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. | |
| Dec 20, 2023 at 19:23 | history | answered | Frank Hopkins | CC BY-SA 4.0 |