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.

4
  • 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? Commented Dec 20, 2023 at 11:19
  • 18
    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... Commented Dec 20, 2023 at 11:21
  • 7
    It sounds like they aren't doing Scrum already. Commented Dec 20, 2023 at 14:55
  • 2
    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) Commented Dec 20, 2023 at 19:17