Agile + DevOps West 2019 - DevOps Engineering
Wednesday, June 5
The 7 Deadly Sins of DevOps
Do you know teams that are merely doing "cargo cult DevOps"? Near the end of WWII, the Allies had airstrips on many islands in the south Pacific. The natives on these islands noticed that when the Allies put the "coconuts" on their ears and spoke into the "banana," the gods would send down a magical flying creature with food and supplies. When the war ended and the Allies left, the natives put the coconuts on their ears and spoke into the banana, and they wondered why the gods failed to bless them, too. They didn't understand headphones or radio transmissions or that someone must be...
DevOps: A Journey of Automation That's Worth the Wait
Continuous delivery is really about one thing: quickly responding to market changes. As with many teams, Shareen Gurley and Narasimha Yalamala's journey began with automation, which seemed never-ending. But to be effective with your DevOps implementation, you need to have solid technical and quality practices to ensure your code is always in a deployable state. If you don’t know exactly where you are going, how will you know when you get there? Join Shareen and Narasimha as they share the prerequisites for creating effective development delivery pipelines, integrated with critical...
AWS Lambda: Best Practices and Common Mistakes
Serverless architectures relieve you of hardware and scaling setup concerns, and AWS Lambda functions are used by many organizations for serverless application development and automating DevOps tasks. But many teams start using AWS Lambda and uncover problems such as running into resource limits, debugging nested Lambda defects, managing code change across dozens of AWS accounts, and many more. Derek Ashmore will provide tips and tricks to make your AWS Lambda functions usable in different contexts and easier to develop and support. He will show you how to mitigate common problems teams...
Thursday, June 6
Using Component Testing for Ultra-Fast Builds
A best practice of software architecture is to design your applications into independent modules or components, with a published contract for interaction between components. This is a principle of the microservices style of architecture, but it also applies to components created in a large monolith. If we can test the functionality of the component independently, and apply a level of trust that those components work, this opens the door to rethinking our continuous integration and continuous delivery strategy, potentially reducing the need for long test suites and many environments. It...
Making the Jump from DevOps to DevSecOps
PreviewOrganizations are moving to DevOps to build and deploy software more rapidly. But as they break down organizational silos to bring together testing, development, and operations, they often avoid or exclude security in their transformational efforts. Leaders in highly regulated organizations are often left wondering, where does my traditional security organization fit into this new DevOps world? How do I know that my applications are becoming more secure, while still getting the advantages of rapid, incremental deployment? Alan Crouch will talk about his experiences with financial,...
Building the Blocks of Trust in Automation
PreviewWhen moving toward automation, establishing trust in the automation test suite is important to unite the team as a whole. Once trust is established in the process and the tests, it becomes crucial to the overall software development lifecycle. Join Sneha Viswalingam as she shares the journey of how her team of manual test engineers contributed to automation, the steps they took to build clean automation and win the confidence of the organization, and how they came to believe that the automation effort has their backs. She'll outline the strategies used to make the tests reliable...
See the Forest, Not Just the Trees: Improving Quality and Flow in a Continuous Delivery World
There are many companies today implementing agile and DevOps practices, usually enabled by a microservices architecture. Most of them are focused on continuously delivering value to their customers within the boundary of a time-bound sprint. If you work at one of these companies or want to move in that direction, how does the quality delivered by your team today compare to in the past? Has it improved, stayed the same, or gotten worse? Are you actively using that data to improve quality? Join Ashwin Desai as he reviews how his company implemented a lean-based approach that allowed them to...