Microsoft Confidential

Krikor MaroukianSr MSM Consultant

krmaro@microsoft.com

+30 695 67 64566

Microsoft Greece, Cyprus, Malta & Romania

28.01.2020

Cross-Domain DeliveryProvide expertise and services that expand and extend the capabilities and boundaries of the Core Technology/Solution Aligned Domains.

Enhanced Solutions Support (ESS)

Remote Delivery Center (RDC)

Architecture and Industry Services (AIS)

Mixed Reality Studios (MRS)

Test

User Experience (UX)

Adoption & Change Management (ACM)

Modern Service Management (MSM)

Global Program Management Office (GPMO incl Vexcel)

Tech intensity = (Tech adoption x Tech capability) ̂ Trust

Tech adoption Tech capability

Adoption & Change Management Modern Service Management

Microsoft Confidential

Modern Service Management is key to cloud trust

Cloud trust =

+ Agile Development

+ Intentional Change Management

+ Modern IT Service Management

76% of IT

leaders report their ITSM strategy is impeding their Cloud strategy

Which is why you need a Modern Service Management Strategy to unlock and accelerate cloud and digital transformation

Mitigate risk

Achieve operation readiness from the start

Reduce costs

Expose potential operational issues and

efficiency gains

Accelerate value realization

Get to a steady state sooner

Microsoft Confidential

runbuild

IT says “we are not quite ready to operate in the cloud”

How do I control Azure Consumption costs? Can I optimize them?

Ops and Engineering are battling... who does what in the new model? What does dev do? What about ops? How do I convince them to work together? Are we organized correctly?

How do I get my help desk ready?

We don’t know which team manages that part of the IT ecosystem.

How does “evergreen” affect my IT processes?

How do I monitor it? (and what?)And who do I call? When? How do I deploy in a way that lets

engineering be agile while ops is comfortable?

Business is frustrated with IT teams’ inability to scale faster.

When customers move to the Cloud, “operational unknowns”

slow down adoption and consumption

Modern Service Management Reference Model

Strategic

Policies and Compliance

IT Adoption

IT Strategy

Value Realization

Operational

Cost

IT Operating Model

Security

Monitoring

Metrics and Reporting

Software and Device

Management

Core Practices and Support

Roles and Responsibilities

Tactical

Cloud Native Tools and

Connectors

Infused AI

Bots

Azure DevOps

Governance and Operations Enable and Automate

Modern Service Management Transformation

Microsoft Confidential

Pursuit Management ESXP (Vanguard)On Consulting, when you are ready to engage with MSM, select IT Service Management in Pursuit Management .

Modern Service Management

Services Portfolio

Offering Management

AskMSM

There cannot be a more important thing

for an engineer, for a product team, than

to work on the systems that drive our

productivity.

So I would, any day of the week, trade off

features for our own productivity.

I want our best engineers to work on our

engineering systems, so that we can later

on come back and build all of the new

concepts we want.

- Satya Nadella, CEO, Microsoft

DevOps is the union of people, process, and tools to enable continuous delivery of value to our customers.

Increase flow

of value

Shorten cycle

times

Continuously

Improve

DevOps

Azure DevOps

ContinuousDelivery

Agile PlanningDashboards

Kanban Boards

Taskboards

Build and TestGit Source Control

Modern Code Workflow

Continuous Integration

Continuous Testing

Package Management

Open Source Compliance

Plan

+

Track

Monitor

+ Learn

Release

Develop +

Test

DeliveryDeployment of app

and infrastructure

PaaS, IaaS and

Containers

MonitoringTelemetry

Diagnostics

Analysis

Our journey to DevOps

Sprint 1August 2010

Sprint 29June 2012

VSTS Preview

Sprint 64April 2014

VSTS GA

Sprint 67June 2014

1ES

Sprint 92Nov 2015

Extensions

Sprint 102June 2016

GVFS

Sprint 124Sep 2016

Five habits we’ve learned so far

Customer Focused

Production First Mindset

Team Autonomy and Enterprise Alignment

Shift Left Quality

Infrastructure as Flexible Resource

DevOps Dojo Approach

SHUIn the beginning stage the student follows the teachings of

the master precisely. The student concentrates on how to do

the task, without worrying too much about the underlying

theory. If there are multiple variations on how to do the task,

he concentrates on just the one way his master teaches him.

HAAt this point the student begins to branch out. With the basic

practices working he now starts to learn the underlying

principles and theory behind the technique. He also starts

learning from other masters and integrates that learning into

his practice.

RINow the student isn’t learning from other people, but from

his own practice. He creates his own approaches and adapts

what he’s learned to his own circumstances.

Customer DevOps Team

Product Owner | Architect | Engineers | Security & Risk SME | Platform Engineer | SRE

Immersive

Learning

Application

Of Learning

Continuous

Learning

SHU

HARI

DevOps Dojo Components

SHU - Training & Practice

1-Click Bootstrap Platform

Azure Lab Service

Azure DevOps

Product Owner | Architect | Engineers | Security & Risk SME | Platform Engineer | SRE

HA - Apply DevOps Practices

Continuous

Planning

Continuous

Quality

Continuous

Integration

Continuous

Security

Continuous

Delivery

Continuous

Collaboration

Continuous

Improvement

Continuous

Operations

RI - Consulting/Coaching

If you knew the plane you were about to board was

maintained to the same level as your current IT

Infrastructure… would you still take your seat?

J A N U A R Y 2 8 , 2 0 2 0

DevOps as a Culture

Krikor MaroukianSr MSM Consultant

krmaro@microsoft.com

+30 695 67 64566

19

© 2020 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Azure, Visual Studio, Windows, and other product names are or may be registered trademarks and/or trademarks in the

U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft

must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided

after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.