Summary

Throughout this chapter, you have been given an insight into the following aspects: how to expose problems within your product delivery process (what we're calling the elephant in the room), the challenges and benefits of using collaborative and engaging approaches to identify these problems, and some effective tools and techniques to help you break down the problems into easily identifiable chunks of work.

Now, you know how to obtain valuable information and data about your problem(s) and have some much-needed actions to work with. You also now know how to inspect. Let's presume these problems revolve around the waste created through long release cycles and a siloed organization. That being the case, you have a very clear objective that will almost certainly address the problems and deliver what the entire business needs. All you now need to do is pull together a plan of attack to implement it. In other words, you now need to adapt. Which is handy as that's what we'll be covering very soon.

Before we do that, I want to delve a little further into the human side of CD and DevOps and highlight two areas that are pivotal to the success or failure of adoption; those being culture and behaviors. In the next chapter, we'll take a deep dive into how culture and behaviors can impact the CD and DevOps adoption—both positively and negatively, and why ignoring this is not a good idea.