Agile Dev West 2018

Much has been written about how to write microservices, but not enough about how to effectively deploy and manage them. Microservices architecture multiplies the number of deployables IT has to manage by at least ten. In that world, tooling to manage cloud deployments and related infrastructure has become essential for success, and Terraform and Docker are increasingly being leveraged to facilitate microservices environments.

On any team, from infrastructure engineering to development to HR, there is always a looming danger of one individual being the only person capable of performing a key task, either because of their technical skills, domain skills, or business experience. The risks of having key-person dependencies—reduced productivity, inaccurate project estimates, morale problems, delays, and business-impacting defects and downtime—are hard to identify and can be even harder to resolve.

As agile goes mainstream, many organizations are only focused on mastering different elements of agile frameworks. Progress is measured by vanity metrics such as velocity and burndown charts. These metrics can turn agile teams into backlog lumberjacks! Teams, ScrumMasters, and leadership must realize that while speed to launch is crucial to delivering software, speed to learning is even more important.

Peer-to-peer Discussion: How Do I Make CD Work in My Environment? Building a successful continuous delivery pipeline is very context specific. Large organizations with legacy code, existing physical environments, regulatory constraints, large monolithic applications, or stove piped organizations often struggle to find a continuous delivery approach that will work for them successfully. If this sounds familiar, this session is for you.