 It's after lunch. I know you all want to fall asleep. This is the worst time to be a presenter So you're going to have to give me a little bit of slack and try and stay awake As part of that this is going to be an interactive workshop Now what most of you probably didn't expect is that I'm actually going to be asking you to do some mathematics through this course So your brains need to be activated. I need you to think I need to be able to do to be fair basic arithmetic But it is coming be aware those of you sitting on tables of one Who are actually participating? Please move into another table. We're going to be doing this in groups. This is a workshop I will try and limit my rambling to a minimum as possible so Let's start with a fairly quick show of hands who here is using Kanban about half of you Okay, all the people who didn't put your hands up. How many of you know what Kanban is? Okay, not too bad. All right How many here has you don't really know what Kanban is you've never used it You just you're here to learn from the very beginning a few of you. Okay, so For those of you who are starting from a very beginning. I am going to go very quickly All right So if you have questions about some of the core principles and some of the core ideas Which I'm over looking and you're unsure just stick your hand up interrupt me And I'll be happy to like go into a little bit more detail and address some of those issues All right now this talk is a little bit different to the majority of Kanban talks Can we be a bit louder? Thank you So this is going to be a little different to the usual Kanban talks that you've probably heard I'm actually not going to talk about Kanban until towards the very end Why because Kanban itself is a tool for visualizing and tracking flow But what is your flow? What is the process flow that you're undertaking going through now each organization? organization every division department team within the organization Interacts with hundreds of processes on a daily basis each one of these processes each one of these Ways of working is in itself what we call a value stream It's called a value stream because at the end of the process you have created something that creates value for the organization If it doesn't create value, then you probably shouldn't be doing it in the first place Does that make sense? So that's the value stream in the value stream map Now the second part which you need to understand is when you are creating those vet these value streams and Defining these process flows We're only really interested in Common processes if you do something once It's not repeatable. There's no points in tracking or visualizing it