Timeline for In Kanban, what should we do with long research tasks?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2020 at 22:05 | comment | added | Barnaby Golden | I don't think that there is a right and wrong way to do this. Best to try an approach and see how it goes. | |
| Jan 4, 2020 at 17:27 | comment | added | Chris Brettini | Thank you! What is the way to implement it in Jira? I don't think we should create many technical tasks instead of one logical task. Maybe we should create sub-tasks of the original task? Is it OK from the Kanban point of view? | |
| Dec 23, 2019 at 16:39 | comment | added | Barnaby Golden | I would expect the team to self-organise who did the work. I'm pretty sure most teams would look to spread the work around, to avoid knowledge being locked in one person's head and to increase the eyes on the analysis tasks. | |
| Dec 23, 2019 at 16:29 | comment | added | Chris Brettini | If the same developer is assigned again and again (this makes sense because this developer better undestands the problem area) then this looks like we are fixing Kanban, like kind of workaround... | |
| Dec 23, 2019 at 7:56 | history | answered | Barnaby Golden | CC BY-SA 4.0 |