Now, how do you get started with continuous delivery? It could be daunting. Well, a lot of teams will say, all right, well, we need to do this, we'll get a continuous delivery expert or a devops expert, we'll wait till we can hire somebody. And getting somebody full time or part time, an advisor from outside, to help coach the team on this, that may be a good idea. But the idea that one person is going to execute the continuous delivery program is the opposite of the point. Because the whole idea is about driving interdisciplinary collaboration, if that sounds familiar. And so, what you really need is to get everyone together, dev, operations testing, and product owner, basically our whole agile team. And just diagram out how your processes actually work. It's basically all the handoffs between those groups. And a lot of teams will find when they do that, they see a lot of good opportunities to make things better, especially small tactical things which taken together can make quite a big difference. And that's a really good way to get started. And if the idea of looking at how you're actually doing things and visualizing that sounds familiar, does it sound familiar? Yes, we talked about that in the practice of kanban. So, you may have already started to do this and gotten into this habit. If so, great. That will really help you here in continuous delivery. Once you've done that it's maybe natural to think, okay, well, we'll start here, and then we'll make our way. It's probably better in most cases to work backwards. So, what happens when you actually release product, and what doesn't go well? And then, what are the antecedents of that, if you work backwards into the pipeline here? One of the things we'll talk a lot about is how you would always want to catch something here, before it goes to this point, to this point. Because you'll catch it faster. It'll get fixed more naturally, because it's top of mind for the the person working on it. And that doing these things in this fashion, small batches adjacent patches, that'll make you a lot more successful. So, create a view of how your process works and then create a hit list from that. And look at what you can standardize and what you can automate. And you probably want to prioritize the big things. What is ops? What is what is dev? What is testing spending a lot of manual time doing? Well, those would be easy wins, relatively speaking. And bigger wins for automation, as you institute that. And then once you get comfortable, you can probably use a continuous integration or continuous delivery platform to start to automate these things and centralize them. Jenkins is one popular alternative that a lot of teams will use. And the idea is just get a very basic working version of this, maybe not all the steps are automated. But just taking that first step and getting things organized and centralized, that'll be a big step forward and really help the team move forward a lot. So, we reviewed some ideas on getting started and how to do that in a very practical, very immediate, something maybe you could do tomorrow kind of way. And as we go through the rest of the videos, we'll talk about some ideas on how these different steps work and things that you may want to consider as you move through them.