Continuous delivery is not just a technical tool. Regardless of whether we want it or not, it creates a fundamental change to the world around software teams, including marketing and customer interaction. Ignoring those changes is dangerous, because it can lead to conflicts with the rest of the company. Embracing those changes and exploiting them opens up new business opportunities. By recognising and taking charge in this transformation, software teams can become much more valuable to the companies around them. This talk will focus on how to unlock all that potential, and turn the fact that your teams can deliver frequently into an engine that will help you outrun your competition. This is a talk for tech and business people.

Cloud will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. As Conway’s Law suggests, though, the quality of your software is a direct reflection on the quality of the culture creating it (just as the structure of your software reflects your organizational structure), making thoughtful decisions about tools and architecture can help. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. "Anyone who says differently is selling something”.

Incremental improvement is better than sequential waterfall delivery. Cloud is not a “silver bullet”, there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it’s worth considering the why and the how of our behaviors, not just the what.