Timeline for Where to (initially) create a task/bug with the Spotify model
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 4, 2020 at 8:50 | vote | accept | Jakob Busk Sørensen | ||
| Aug 4, 2020 at 3:07 | comment | added | Daniel | Fair enough. Given the constraint, just creating it where it logically seems to go and letting it kove might be fine. You could also try to create a method by which teams make that choice. That would require a shared space that teams look at regularly and say "that looks like it could be ours". Most teams newer to scrum feel pressure to fill the sprint and gence push back on any extra work, so you would also need a balancing motivation for them to actually take on the bugs without being assigned. | |
| Aug 3, 2020 at 16:59 | comment | added | Jakob Busk Sørensen | I agree, that we are most likely having these issues, do to a less-than-optimal implementation of the model (or the idea behind it). But for now, what would you recommend doing? Creating the bug where you think it belongs, and then move it, once properly investigated? | |
| Aug 3, 2020 at 14:41 | history | answered | Daniel | CC BY-SA 4.0 |