 Fine on your table is some stuff that you're going to work with so that's the materials for the workshop Okay, so I'm going to start with some questions Who here is doing TDD in your teams? Okay, if you're not coding yourself if you're a scrum master of your teams are What is the point of defining a test before you start? Sorry Fail only say that again You do what is required just what is required Anything else? You'll know when you're done. Yes, and you know where you're going to right you've defined up front where you're going So what is continuous improvement? Yes, think about these two things together So in this workshop away before I go there, how do we do our inspect in a depth? What is the process we use or you guys use retrospectives anybody doing anything else? Okay, yeah Problem-solving so typically in agile we use retrospectives From lean. There's a three thinking in Kaizen, which is where the title of this workshop comes from and They're all come from something called the scientific method And what is that? There are many explanations, and I'm going to do it as visually as I can We start off by looking clearly at what our environment is and Then we question and analyze we look deeply into first we look at and then we look in From that we formulate an idea about how the system can be changed what would be valuable and then we implement our experiment and That would be in the course of our sprint or however we determine our the plan Then we stop and we check our results. That's typically where our retrospectives come in right we assess the implications of the change in the system or Do we so the point of this talk is That I'm not getting I think this area over here From months to months with sprint to sprint however long your sprints are week to week We make a change and we see at the end of those sprint whether we have succeeded in what and We measure our success and then we