Kanban Fishbowl Session
David J. Anderson leads a fishbowl session dedicated to sharing experiences and lessons learned from introducing Kanban to various organizations.
David J. Anderson leads a fishbowl session dedicated to sharing experiences and lessons learned from introducing Kanban to various organizations.
Spike Morelli discusses best practices behind the creation of Programmatically Generated Images, a tool for building and deploying system images that remain unchanged through QA, staging and production.
Sam Newman and Chris Read describe the architectural change of a large European website by introducing a caching layer based on Squid in order to scale out to handle increased demand, and the cultural change done by breaking down the dev-ops silos.
Jez Humble talks on the importance of Continuous Delivery for a business, outlining the foundational principles and practices to be implemented for a successful CD, explaining how to do continuous integration, various ways of testing, canary releasing, and migrating data.
Stephen Nelson-Smith’s presentation is a case study and lessons learned by implementing Agile and Lean practices by both the development and operations team in an attempt to overhaul the entire development, testing, staging, and production process of a UK governmental website.
We know that solving DevOps problems improves your business operations and improves the bottom line, but how do you do you explain that to your CEO or CFO? How do you get the executives to buy in and invest in DevOps solutions?

Much of the public discussion about DevOps focuses on Web Operations. This panel is about taking the lessons of DevOps to other types of IT.
Examining the role of monitoring and testing techniques in solving DevOps problems.
Examining the role that cloud technologies can play in solving DevOps problems and the role that DevOps solutions can play in getting the most out of cloud technologies.
Changing tools is easy when compared to changing people and processes. How can we cultivate an organization’s culture to identify and solve DevOps problems?
Automation is essential to DevOps. The infrastructure as code concept drives many of today’s cutting edge automaton techniques. What is it all about? Where are its limitations?