introducing change while preserving engineering velocity

32
Introducing Change while Preserving Engineering Velocity Dianne Marsh @dmarsh dmarsh@netflix.com FlowCon 2014

Upload: dianne-marsh

Post on 31-Oct-2014

320 views

Category:

Software


0 download

Tags:

DESCRIPTION

Netflix moves fast and Engineering Tools is charged with enabling that velocity. With that goal in mind, we made a lot of tooling changes in the past year. But with change, comes cost. We are in the process of migrating several systems near and dear to our developers, including our version control system, deployment tool, and operating system for our AMIs. Our goal is to do this while minimizing impact on our customer teams, How did we do? What could we have done better? What aspects of Netflix's culture enabled this? And, most importantly, what can you take back to your own companies regarding the importance of making improvements while mitigating the tax on your teams?

TRANSCRIPT

Page 1: Introducing Change while Preserving Engineering Velocity

Introducing Change while Preserving Engineering Velocity

Dianne Marsh @dmarsh

[email protected] !

!

FlowCon 2014

Page 2: Introducing Change while Preserving Engineering Velocity

Engineering Tools Charter

We provide build and deployment tools that support engineering teams’ innovation. We enable velocity through investments in tooling and customer

engagement.

Page 3: Introducing Change while Preserving Engineering Velocity

We don’t

Build, Bake, or Deploy for Teams or

Manage Configurations

Page 4: Introducing Change while Preserving Engineering Velocity

Planned Migrations in 2014

• Centos to Ubuntu AMI

• CBF to Nebula/Gradle

• Upgrade Continuous Delivery Solution

• Perforce to Git

• Get Tools out of Data Center

Page 5: Introducing Change while Preserving Engineering Velocity

CultureFreedom and Responsibility

http://www.slideshare.net/reed2001/culture-1798664

Page 6: Introducing Change while Preserving Engineering Velocity

Context, not Control

Page 7: Introducing Change while Preserving Engineering Velocity

With Freedom comes Responsibility

Page 8: Introducing Change while Preserving Engineering Velocity

Meet with Key Stakeholders

Page 9: Introducing Change while Preserving Engineering Velocity

Describe the “Paved Road”

Page 10: Introducing Change while Preserving Engineering Velocity

Support Velocity !

Customer Engagement Team

Page 11: Introducing Change while Preserving Engineering Velocity

Embed Customer Engagement Team on Tools Development

Page 12: Introducing Change while Preserving Engineering Velocity

Migration Goals

• Engage with our customers

• Share the cost of change

• Encourage self-sufficiency

Page 13: Introducing Change while Preserving Engineering Velocity

Broadly Socialize the “Why”

Simplicity

SpeedReliability

Repe

atab

ility

Business AgilityVisibility

Core Competencies

Page 14: Introducing Change while Preserving Engineering Velocity

Don’t Worry about the Easy Sells

Page 15: Introducing Change while Preserving Engineering Velocity

Provide Guidance

Page 16: Introducing Change while Preserving Engineering Velocity

Dates, or It Won’t Happen

Page 17: Introducing Change while Preserving Engineering Velocity

But, Be Flexible

Page 18: Introducing Change while Preserving Engineering Velocity

ROADSHOW

Page 19: Introducing Change while Preserving Engineering Velocity

Respect the Journey

Page 20: Introducing Change while Preserving Engineering Velocity

Build Tooling to Support Migration!

Page 21: Introducing Change while Preserving Engineering Velocity

Let your Tools do the Talking

Page 22: Introducing Change while Preserving Engineering Velocity

How did we do?

Page 23: Introducing Change while Preserving Engineering Velocity

Some Data …

Page 24: Introducing Change while Preserving Engineering Velocity

But … (http://upload.wikimedia.org/wikipedia/en/4/45/DiffusionOfInnovation.png)

Page 25: Introducing Change while Preserving Engineering Velocity

Room for Improvement

Page 26: Introducing Change while Preserving Engineering Velocity

More Outreach!

Page 27: Introducing Change while Preserving Engineering Velocity

Increase Transparency (Dashboards)

Page 28: Introducing Change while Preserving Engineering Velocity

Orient (vs. Other Teams)

Page 29: Introducing Change while Preserving Engineering Velocity

Custom Training for Custom Solutions

Page 30: Introducing Change while Preserving Engineering Velocity

Google for the Rest!

Page 31: Introducing Change while Preserving Engineering Velocity

Your Suggestions?

Page 32: Introducing Change while Preserving Engineering Velocity

Thanks!

Dianne Marsh (@dmarsh) [email protected]