DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering System"

•Download as PPTX, PDF•

3 likes•431 views

This document introduces Sam Guckenheimer and Ed Blankenship and discusses Microsoft's goal of creating a single engineering system (1ES). The purpose is to enable any developer to access and reuse source code across the company, get rewarded for creating popular components, and have changes instantly visible. In practice, this means scaling Git for enterprise use, promoting a live site culture, and creating a common telemetry pipeline to measure usage and engineering metrics. The goal is to have self-forming teams and determine if 1ES is achieving its goals like supporting 4x user growth.

Technology

About Us
Sam Guckenheimer
Product Owner, Visual Studio Cloud Services
13 years Microsoft
30 years software industry
@SamGuckenheimer
https://aka.ms/devops
Ed Blankenship
Product Manager, DevOps, VSTS/TFS
5 years Microsoft
15 years software industry
@EdBlankenship
https://about.me/edblankenship
https://engineering.microsoft.com/

Purpose of One Engineering System
If you want to go fast, go alone. If you want to go far, go together.

Before 1ES
Unintended
consequence:
No reuse
would go
unpunished.

An engineering north star…
…the source across the company is available to anyone
…any dev can offer improvements to anything in the company
…the IP the company has built up over the years is made of re-usable components
…anybody can find and potentially re-use components from anywhere else
…devs are rewarded for creating popular components
…there is zero lag from when a dev makes a change & when the rest of the company sees it
… build and test time is directly proportional to the change made
…devs can move to another team and already know how to work

Live Site Culture and Engineering
Live Site Health
Time to Detect
Time to Communicate
Time To Mitigate
Customer Impact
Incident prevention items
Aging live site problems
Customer support metrics
SLA per customer account
(SLA, MPI, top drivers)
Engineering
Bug cap per engineer
Aging bugs in important
categories
Pass rate & coverage by
test level
Velocity
Time to build
Time to self test
Time to deploy
Time to learn
(Telemetry pipe)
Usage
Acquisition
Engagement
Dedication
Churn
Feature usage

Common Telemetry Pipeline
Combines
high volume ingestion
fast queries over very
large data sets
text search structured
and unstructured data

Self-forming teams
https://aka.ms/SelfFormingTeams

Is 1ES Working?
4x active user growth in 2 years to 62,000

DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering System"

What's hot

Continuous Delivery e-book

Zend by Rogue Wave Software

Meteorjs

Radhouen Assakra

Transform Agile Development With Practical DevOps

Gaurav Sharma

More and more companies worldwide are excited about DevOps and the many potential benefits of embarking on a DevOps transformation. The challenge many of them are having, however, is figuring out where to begin and how to scale DevOps practices over time. These challenges can be especially daunting in large enterprises. In this webinar we will discuss a maturity model for framing your transformation, then focus on analyzing your deployment pipeline and identify existing inefficiencies in software development and deployment.

Starting and Scaling DevOps

Jules Pierre-Louis

Tailoring your SDLC for DevOps, Agile and more

Jeff Schneider

My Career Journey: An Unconventional Path into DevOps

VMware Tanzu

ncorporating DevOps – The Phoenix Project Simulation Businesses are demanding ever shorter release cycles for new applications. Traditionally ‘Operations’ is seen as a barrier with lengthy bureaucratic controls and delays in provisioning production systems. DevOps is a growing movement for shortening development and deployment and integrating Development and Operations. However, this requires a mind-set shift, new behaviours and a cultural shift in both Development and Operations. Traditionally suspicious of each other, they must now work closely together. Yet many companies are struggling to adopt and deploy DevOps and how to change the culture. The “Phoenix Project” Simulation game is based upon The Phoenix Project. Parts Unlimited is in trouble. Newspaper reports reveal the poor financial performance of the organisation. The only way forward to not only save the company but to make it competitive and profitable is “The Phoenix Project” which represents an IT enabled business transformation, with Retail Operations as the business owner of this project. The VP of IT Operations is asked to take the lead of the IT department and ensure that “The Phoenix Project” will be a success. But the VP of IT Operations is facing a tremendous amount of work. A huge backlog of issues, features and projects. Are you up for the challenge…?

The Phoenix Project DevOps Simulation - Paul Wilkinson

Pink Elephant

DevOps and Continuous Delivery Reference Architectures (including Nexus and o...

Sonatype

DevOps Culture & Methodology Intro

Najib Radzuan

Keynote: The Phoenix Project: Lessons Learned - PuppetConf 2014

Puppet

Walk This Way - An Introduction to DevOps

Nathen Harvey

Devops at SlideShare: Talk at Devopsdays Bangalore 2011

Kapil Mohan

So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.

Vmware2021 why even devop nicolefv

Nicole Forsgren

Waste Driven Development - Agile Coaching Serbia Meetup

Lemi Orhan Ergin

Introduction to devops - update 2017

gjdevos

From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use. Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project. In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

DevOpsDays Tel Aviv

1 year has passed since my Devops laboratory talk in Devopsdays Melbourne and we haven't stopped experimenting. After all the buzz and great conversations at Devops days I decided to extend the talk with a few more experiments on top of the previous presentation. This talk was first presented in Last.conf Melbourne on June 2016. The objective is no matter were your company is in terms of adopting a Devops culture/mindset there is always opportunities to try something new. The experiments covered include: E0. At the beginning, there was devs and ops E1. Placements E2. The tooling team (code name Gandalf) E3. Secondments E4. Ops as an attribute of Business areas E5. The era of Guilds E6. The raise of the Delivery Engineering teams E7. Sec + DevOps E8. Leverage vs Autonomy E9. Finance + DevOps E10. ????

The devops laboratory - 1 year later

Javier Turégano Molina

DevOps - Understanding Core Concepts

Nitin Bhide

Traditional development methods just can’t keep up. Backlogs balloon, projects are postponed, and outside consultants are brought in to meet deadlines. To break free of this cycle, you need a better way to work. Though DevOps is not a cure-all, it’s a critical part of the answer, bringing development and IT operations together to create a streamlined system for software development and deployment. More a method than a prescription, DevOps is a collection of engineering, behavioral, and organizational practices focused on moving rapidly, safely and sustainably from idea to reality. To implement DevOps, any organization needs to make big changes — changes that impact culture, processes and people.

Effective devops

Mohammed Aboullaite

Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...

David Walker

What's hot (20)

Continuous Delivery e-book

Meteorjs

Transform Agile Development With Practical DevOps

Starting and Scaling DevOps

Tailoring your SDLC for DevOps, Agile and more

My Career Journey: An Unconventional Path into DevOps

The Phoenix Project DevOps Simulation - Paul Wilkinson

DevOps and Continuous Delivery Reference Architectures (including Nexus and o...

DevOps Culture & Methodology Intro

Keynote: The Phoenix Project: Lessons Learned - PuppetConf 2014

Walk This Way - An Introduction to DevOps

Devops at SlideShare: Talk at Devopsdays Bangalore 2011

Vmware2021 why even devop nicolefv

Waste Driven Development - Agile Coaching Serbia Meetup

Introduction to devops - update 2017

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

The devops laboratory - 1 year later

DevOps - Understanding Core Concepts

Effective devops

Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...

Viewers also liked

SAP’s DevOps Journey: From Building an App to Building a Cloud Marc Ng, Cloud Infrastructure Engineering & Automation, SAP SAP has been using a DevOps & Continuous Delivery approach for building its web and mobile apps for several years, and is now building and running a global cloud at the scale needed to support the digital transformation needs of its customers. This talk recaps the story of how SAP originally adopted DevOps practices before moving on to describe how the Cloud Infrastructure Services team is building and operating its 3rd generation cloud automation system using microservices, containers and open-source software. DevOps Enterprise Summit San Francisco 2016

DOES16 San Francisco - Marc Ng - SAP’s DevOps Journey: From Building an App t...

Gene Kim

Predictability: No Magic Required Julia Wester, Improvement Coach, LeanKit When you merge onto a freeway and are stuck in bumper-to-bumper traffic, you know right away that its going to be a long trip. Similarly, you can predict the cycle time of your work before it is finished without time consuming, and often incorrect, estimation. Sound like magic? Fortunately for all of us, it's not. This talk explains the basics of queueing theory; demonstrates how allocation models and pull policies affect the cycle time of work; discusses the effects of batch size and variability on queues; and teaches how to successfully monitor your workflow to get leading indicators of effectiveness. With this information, you'll be doing better forecasting, and achieving better outcomes, in no time!

DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required

Gene Kim

DOES SFO 2016 - Scott Willson - Top 10 Ways to Fail at DevOps

Gene Kim

DevOps news is dominated by discussions about tools, and with good reason. It's not unusual for the amount of infrastructure-related code in a system to approach or even exceed the amount of code dedicated to the actual problem the system is solving, even in small systems. As our systems scale in size and complexity, we invest an ever increasing amount of resources into building solutions to help manage our our complex technical systems. And rightly so. What's often overlooked, however, is the human component of our systems. All too often our approaches to tools, processes, and systems management attempt to remove humans rather than empower them. I'll make the case that humans are not a source of entropy to be safeguarded against in our systems, but rather a fundamental source of resilience and even efficiency. We'll discuss ways that we can use this point of view to our advantage when constructing our systems to move faster without sacrificing safety. We'll look at things like tools and our interactions with them, team collaboration, and even organizational structure and policies. We've had plenty of talks about building for web scale, cloud scale, and even planetary scale. Let's spend some time talking about designing for human scale.

DOES SFO 2016 - Mark Imbriaco - Lessons From the Bleeding Edge

Gene Kim

2 years ago at DOES14, I presented “Vision Versus Execution: Implementing Continuous Delivery”. I shared how we achieved a big Continuous Delivery win – increasing software test coverage and delivery velocity and efficiency. Since then, we have been busy scaling DevOps, Continuous Delivery and Lean principles across teams and practices throughout Urban Science. This rollout included both a cultural aspect, as well as an implementation of a centralized, shared, self-service automation solution for our teams – enabling them to “opt-in” to an automated pipeline. In this talk I will present anecdotes and learnings gathered through our experience over the past two years and discuss the challenges and the value of scaling DevOps across the organization.

DOES SFO 2016 - Marc Priolo - Are we there yet?

Gene Kim

DOES SFO 2016 - Rich Jackson & Rosalind Radcliffe - The Mainframe DevOps Team...

Gene Kim

Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations. In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.

DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?

Gene Kim

Tempo. Most people are familiar with it in the musical sense. It’s the speed, cadence, rhythm that the music is played. It drives the music forward - and pulls it back. But there’s more to tempo than a musical beat. In war, like in business, tempo - the speed at which you can transition from one task to the next - is a critical component for victory. No single person nor department owns tempo. Somebody can’t just shout, “I now control the tempo,” and take charge. If you operate at a faster tempo than your cycle time allows, then you’ll get thrashing. The rate of tempo emerges organically as companies move around that action loop of sensing, deciding and acting. Tempo emerges from the convergence of architecture, infrastructure, organization, and mindset. All these things have to align to achieve tempo. None of them can be changed in isolation. In this talk, we will look at different models for transforming an organization to high tempo and high performance. We'll see how that can get derailed and what to do about it.

DOES SFO 2016 - Michael Nygard - Tempo, Maneuverability, Initiative

Gene Kim

DOES SFO 2016 - Ross Clanton and Chivas Nambiar - DevOps at Verizon

Gene Kim

In my previous years’ talks at DevOps Enterprise Summit, I spoke about starting and scaling of DevOps at Capital One; importance of Open Source, Open Technology and Innovations in DevOps. This year, I will present Capital One’s journey of maturing in DevOps and Continuous Delivery. My presentation will cover our current areas of focus: Delivery Pipeline, Flow and Measurements. I will also share some of the problems we faced and what we did to solve them.

DOES SFO 2016 - Topo Pal - DevOps at Capital One

Gene Kim

Netflix Case Study - AWS

Heath Dorn

Rakuten and Microsoft talk DevOps in Real World

Tsuyoshi Ushio

The Talent You Need is Already Inside Your Company Damon Edwards, Co-Founder, SimplifyOps, Inc “Buy vs Build” is a decision made all throughout an enterprise. We vigorously debate either position when it comes to our technology and tools. But what about our people? Conventional wisdom holds that, if an enterprise seeks a transformation, it must go into “buy” mode and acquire as much talent as possible from the outside. However, in reality this is an expensive strategy with a low success rate. Putting aside the obvious problem of there being a very limited number of “the best” to spread across an entire industry, the “buy” strategy is still largely based on hope. You hope that the new people will bring the right ideas that will automatically spread. You hope that the new people will have experience that can be translated to your business. But, more often than not, the hope of the income new is undermined and overwhelmed by the same systemic issues that caused your current problems. This talk is about a tactical set of actions that leaders can take to find and fix their company’s systemic issues. If you fix the system, you’ll be able to de-risk the new. If you fix the system, you’ll find a truth that just isn’t discussed: the talent you need to succeed is already inside your company. DevOps Enterprise Summit San Francisco 2016

DOES16 San Francisco - Damon Edwards - The Talent You Need is Already Inside ...

Gene Kim

When Ops Swallows Dev Scott Prugh, Chief Architect & VP Software Development & Operations, CSG International Erica Morrison, Director, Software Development, CSG International CSG has been on an Agile and Lean journey to continually shorten feedback loops in its SDLC and Operations Processes. This began with moving from waterfall to agile and deploying cross functional dev teams. Today, we have taken this transformation further by deploying cross functional product delivery teams that Design, Build, Test and Run their products. Join us to discover the things that went as expected and the surprises we discovered in this journey. DevOps Enterprise Summit San Francisco 2016

DOES16 San Francisco - Scott Prugh & Erica Morrison - When Ops Swallows Dev

Gene Kim

Influencing Higher Education to Create the Future DevOps Workforce Charles Betz, Coordinator, Minnesota State Digital Curricula Initiative "Where will we find the talent?" The feedback loops are slow for higher education, and institutions are only now beginning to respond to the opportunities of DevOps. How can we accelerate this process? This fast-paced talk will cover both macro- and micro-scale efforts. Over the summer, 11 faculty from Minnesota teaching colleges worked with industry thought leaders to draft a report, “Digital Curricula: Toward next-generation IT education.” The report (including a survey on current digital workforce) compiled hundreds of learning objectives from leading digital and DevOps practices, for instructors and commercial trainers around the world to use in course development. This report (free and sponsored by the Advance-IT Center of Excellence in the Minnesota State University System) is being distributed this October to hundreds of computing and IT faculty across the 6th-largest education system in the U.S. and will be presented here for the first time to an industry audience. As a worked example at the course level, the University of St. Thomas offers a survey course on IT delivery, using a “flipped model” with recorded lectures and experiential labs. An open source, 8-node, software-defined virtual cluster based on open technologies is used to illustrate continuous delivery, infrastructure automation, and Agile concepts for the course’s 12 open source lab sessions, as well as collaborative topics such as product management, work management, and operations. Come hear discussion of the motivations, teaching philosophy, technical practices, and results of this pioneering course. DevOps Enterprise Summit San Francisco 2016

DOES16 San Francisco - Charles Betz - Influencing Higher Education to Create ...

Gene Kim

The Latest: What We Learned from the 2016 State of DevOps Report Dr. Nicole Forsgren, CEO and Chief Scientist, DevOps Research & Assessment LLC Jez Humble, CTO, DevOps Research & Assessment LLC Four years and 25,000 respondents later, and we have learned a lot about what makes IT and organizational performance awesome. This year we include insights into security, containers, trunk-based development, and lean product management. Tune in for practical take-aways to make your teams' technology transformations even better. DevOps Enterprise Summit San Francisco 2016

DOES16 San Francisco - Nicole Forsgren & Jez Humble - The Latest: What We Lea...

Gene Kim

Source code: Just put it in git, right? Enterprise scale? Github! But what about when you have a *lot* of source code? Thousands of repositories? No problem! Github Enterprise or Bitbucket Server to the rescue! Now: Add PCI & SOX. Confidential information. Separation of concerns. Audit. SSO. Centralized SSH key management. DR. Geographic diversity. This is the part where you roll up your sleeves, and start doing the real work. This talk starts where the vendors stop- discussing workflows to keep work moving, security & audit protections to ensure code integrity, and automation to connect to other enterprise systems.

DOES SFO 2016 - Matthew Barr - Enterprise Git - the hard bits

Gene Kim

DOES SFO 2016 - David Habershon - Ministry of Social Development New Zealand

Gene Kim

After an initial DevOps transformation as a company, we had to grapple with how to scale and grow the talent and workforce to build a NextGen DevOps-minded company of 18,000+ people. We have built a number of programs to expand awareness, encourage growth mindsets, and drive workforce development. We will share the different ways we are working to "Build Brilliant Teams" to drive our DevOps transformations.

DOES SFO 2016 - Paula Thrasher & Kevin Stanley - Building Brilliant Teams

Gene Kim

Technology Transformation: How Team Values Boost Customer Value Opal Perry, Divisional CIO, Claims, Allstate Insurance At Allstate, the largest publicly held personal lines property and casualty insurer in America, we constantly innovate for the good of our customers. It’s part of who we are and the legacy we’ve been building since 1931. Recently, we set about recasting the organization's technical and engineering discipline to make it core to the company, and moving technology up the value chain. But technology is just one piece of the transformation. Opal will discuss how an explicit focus on culture and values, together with new ways of working, empower product teams and bring valuable technology to customers with greater speed and agility.

DOES16 San Francisco - Opal Perry - Technology Transformation: How Team Value...

Gene Kim

Viewers also liked (20)