IMO Kanban (i.e. "pull") is better suited for reactive work (bug fixing, QA, support, ops, etc.). There is a third approach: to give autonomy to the team so th

IMO Kanban (i.e. "pull") is better suited for reactive work (bug fixing, QA, support, ops, etc.). There is a third approach: to give autonomy to the team so that it can distribute and perform tasks as it sees fit. There may be hints about priorities, such as a must-to-have or nice-to-have. See: Shape Up Method or Informal Mini Waterfall SDLC (design->plan->build(iteration)->ship) used by FAANG. Once you have a written design document (especially if you wrote it yourself), you don't need a ticketing system like Jira. In many places we have only used tickets for bug reports and not for tasks.