Kanban is well-suited for teams triaging work across focus areas.
This will particularly be the case when the team owns multiple matured properties which they may frequently change focuses between. Released changes are ad hoc and not necessarily pursuing a larger plan, at least an immediately cohesive iteration. The team does not need to be cross-functional to achieve its goals.rG2
Dustin Moris Gorski, “When to Use Scrum? Waterfall vs. Scrum vs. Kanban vs. Scrumban - Dusted Codes,” Dusted Codes (blog), November 8, 2015, https://dusted.codes/when-to-use-scrum-waterfall-vs-scrum-vs-kanban-vs-scrumban. (See notes.)