Summary
In this chapter we talked about roles. Kanban is not prescribing any roles; on the contrary, it is telling you to initially not change any of your roles. The roles we have suggested are just roles we have seen improving the system in other places.
Examples of roles we talked about are Kanban Master, who is the master of the process and acts as a shield for the team; and the Product Owner, who prioritizes the backlog and communicates with the stakeholders.
We have also suggested a couple of meetings you could pick from to improve your system. The most important one is the Retrospective meeting since that´s the meeting focus on how to improve the process. In the next chapter, it's finally time to start using Kanban for real. You will get an impression of how the first day's schedule could look.
