The Kanban Lens: going from from "Teams everywhere" to "Services everywhere"

"Kanban is a way of seeing", we like to say, and one of the things you see with Kanban is "services". But seeing services sometimes can be trickier than it sounds, especially if you're new to Kanban. Teams, on the other hand, is something we are more used to seeing and working with. To complicate things, sometimes "team == service", but most of the times that's not the case.

You can apply Kanban both to teams and services, but the resulting Kanban system normally accomplishes a very different "agenda", so learning to differentiate between the two (including when "team == service") and to pragmatically define a service boundary is a critical skill for a practitioner of the Kanban Method.
In this session, we'll show you an exercise you can use to identify a service and its pragmatic boundaries, and then we'll open the floor for discussion of topics and questions that emerge when thinking about how to move from seeing "teams everywhere" to "services everywhere".