Abstract

Transitioning an organization to DevOps in spirit and not just in name can be incredibly challenging as existing silos and reporting structures will likely not be ideal. After a quick look at a number of transition anti-patterns, we'll go into how best to design an organization structure using a virtual team view. Virtual team initiatives themselves are not new yet the trick is effectively identifying and putting together the right mix of people's capabilities for the type of product (legacy, mid-cycle, lean MVP, etc). Using a combination of a Wardley diagram and Spotify's Guild model we can build an effective mapping of the needed culture and skill sets regardless of where in the spectrum between microservices and a matrix your organization lies. We'll also dig further into actionable strategies for affecting change and high-level systems design for collaboration.

Bio

Alec Lazarescu is a 17 year veteran of the digital education domain as a software engineer, DBA, director, and chief architect. Hes currently CTO of LearnBop, a K-12 education startup. Hes passionate about helping individuals and organizations learn and work more effectively and strive for data-driven continuous improvement. Alec has been a speaker at Amazon, Microsoft, and other community events and a recognized leader in DevOps transformation working at both large and small companies. Hes had articles featured on http://devops.com/author/alecl/ and also blogs at http://www.pragmaticdevops.com/ and tweets through @alec1a. He is also currently exploring how bots can work together with software delivery teams.

Note: We will start at 6:30 exactly.

As always, a group of us will hang out afterwards at a bar nearby.

We like to hang out at Rye, which is at 11 W 17th St, New York, NY 10011, between Avenue of Americas and 5th. They have both drinks and food. http://ryehousenyc.com/