Team-first technologist at Skelton Thatcher Consulting. DevOps advocate with a diverse background as developer, build manager and QA lead. Manuel enjoys helping organizations adopt test automation, continuous delivery and cloud, from both technical and human perspectives. He has worked on a range of technologies (Java, .Net, web, mobile) and industries (banking, telecom, legal, defense and aviation). Co-author of the books “Team Topologies” and “Team Guide to Software Releasability“. Also InfoQ DevOps lead editor, co-organizer of DevOps Lisbon meetup. Tweets @manupaisable, blogs at skeltonthatcher.com
Everyone is Part of Continuous Delivery
The true value of Continuous Delivery lies beyond the Jenkins, the Dockers and the cloudz. Its true value will be found when it involves and caters for the needs of everyone in the delivery organization, from business owners, to developers, testers, operations, etc.
Delivery pipelines are an excellent tool for visualizing workflow. But they’re even better as collaboration tools! A pipeline that accurately maps the flow of work will highlight recurring bottlenecks and waiting times, often due to work hand-offs between teams working in isolation.
Unfortunately, pipelines often lead to Continuous Delivery exclusion because they’re only focusing on the (automatable) technical bits. But if your organization needs to deliver fast(er), don’t buy a Ferrari that only takes 2 people… Prefer a family car that can take everyone comfortably at the max speed that is safe and reliable!
In this talk we will go through concrete pipeline scenarios for different personas in the organization, demonstrating their full transformation power.
Key takeaways include:
a) understanding the benefits of making your pipeline an accurate visualization of the full workflow (beyond the technical bits)
b) understanding the need to bring everyone along in this journey to deliver on the promise of faster and more reliable software development
Workshop: Team design for effective software systems
In any medium to large organization, Agile development teams must collaborate with other teams in order to get software actually running in production and used by customers. The emergence of DevOps demonstrated there was a gap between how software was developed and how software was delivered and operated.
For effective cloud-connected software systems we now face the need to organize our teams in ways that maximize throughput but also quality and predictability. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
In this workshop you will learn how to design your organization for modern, cloud-connected software systems, covering topics such as: fundamental team topology types and anti-types; how and when to use the fundamental team topologies; the dynamics of team design and how teams should evolve; heuristics for discovering new topologies.
On completion of the workshop, you should have a sound understanding of which team topologies to apply in different circumstances and why.