Timeline for How to distribute development and bug fixes tasks
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2023 at 19:17 | comment | added | Frank Hopkins | while that would make the management bit more clearly reflect the requirements, I don't think it would solve the developers issue, it would just stare him more into the face ;) (but it would at least reflect the fact that bugs apparently cannot wait a week) | |
| Dec 20, 2023 at 14:55 | comment | added | Simon B | It sounds like they aren't doing Scrum already. | |
| Dec 20, 2023 at 11:21 | comment | added | Philip Kendall | If you don't have enough people to work on all the bugs coming in, that's a different problem and not one a different development methodology can solve... | |
| Dec 20, 2023 at 11:19 | comment | added | Cap Barracudas | Yeah, I was researching that right now. It seems this should be the case. But even in Kanban, you should not stop a task in progress and do another, right? Just change the top of the backlog? Or you can freely do context switching? | |
| Dec 20, 2023 at 11:10 | history | answered | Philip Kendall | CC BY-SA 4.0 |