0% found this document useful (0 votes)
45 views

Level 100 - Dev-Ops Framework

The document discusses Microsoft and DevOps. It defines DevOps as development and operations collaboration and notes it can refer to both a job title and a philosophy of faster and smaller releases through automation. It outlines three ways of thinking about DevOps: systems thinking, feedback loops, and experiments. It then discusses people, process, and tools as important aspects of DevOps adoption. Finally, it provides an overview of Microsoft's DevOps tools and ecosystem across the development lifecycle from plan to monitor and learn.

Uploaded by

kamal haridan
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
45 views

Level 100 - Dev-Ops Framework

The document discusses Microsoft and DevOps. It defines DevOps as development and operations collaboration and notes it can refer to both a job title and a philosophy of faster and smaller releases through automation. It outlines three ways of thinking about DevOps: systems thinking, feedback loops, and experiments. It then discusses people, process, and tools as important aspects of DevOps adoption. Finally, it provides an overview of Microsoft's DevOps tools and ecosystem across the development lifecycle from plan to monitor and learn.

Uploaded by

kamal haridan
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

Microsoft and Dev-Ops

What is DevOps? “Development


and Operations
collaboration”

“Automation

“Faster and
“A job title” smaller releases”
The first way (systems thinking)

DEV OPS
The second way (feedback loops)

DEV OPS
The third way (experiments)

DEV OPS
The DevOps conversation

People Process Tools


DevOps adoption

Source: Saugatuck Technology Inc. © 2014


www.saugatucktechnology.com
Tools

Source: Saugatuck Technology Inc. © 2014


www.saugatucktechnology.com
Microsoft – the open Cloud for DevOps
"Microsoft’s comprehensive hybrid story, which spans
applications and platforms as well as infrastructure, is
highly attractive to many companies, drawing them
towards the cloud in general”
LYDIA LEONG,
GARTNER

Microsoft a Leader in Gartner Magic Quadrants


Public Cloud IaaS (May 2015) Enterprise Application PaaS (Jan 2014) Application Lifecycle Management (Feb 2015) Integrated Software Quality (August 2014)
Microsoft
Microsoft

Microsoft
Microsoft
Microsoft
Our Own DevOps Journey
Flow Backlog
The flow of value as code moves through How an organization defines and manages
the system from developer environment to requirements and how effective they are.
production, and the rate at which business
value is delivered in the form of software. Evidence
Characteristics and behaviors that
Agile Schedule and Teams demonstrate how an organization uses data
Behaviors and characteristics that reflect in decision making, including code analysis,
team organization and work schedule. test results and real-world usage metrics.

Technical Debt Production


Behaviors and characteristics that define how Refers to how an organization manages
an organization thinks about the decisions software in its production environment,
they make that incur technical debt as well including how it detects and responds to
as how they discover and manage technical unexpected events.
debt that is accrued throughout the
application lifecycle. Cloud Infrastructure
Refers to the behaviors and characteristics of
how the organization approaches and
manages the core infrastructure that their
systems and apps run on.
DevOps
1 Plan 4 Monitor + Learn

Development Production

2 Develop + Test 3 Release


DevOps drivers
Plan Monitor + Learn

• Prioritization of investments is not • Troubleshooting performance and


based on real-world usage patterns availability is often difficult

Development Operations

• Agile methodologies speed up the • Operations cannot keep up with


development cycle development and release fast enough

Develop + Test Release


Plan
It starts with an idea – and a plan
how to turn this idea into reality …
Project starts

Manage work

Develop + Test 1

Track progress Plan


Develop + Test
Once the iteration starts, developers
turn great ideas into features … 2

Write Code

Unit Testing

Version Control

Build

Build Verification

Release
Dev/Test issues
Infrastructure Maintaining a development and test infrastructure in
Cost Concerns physical, on-premises hardware is costly.

Inability to Long procurement cycles, effort, admin overhead and


Deliver Value resource contention limits the team’s ability to deliver value.

Governance/ Self-provisioned ‘under the desk’ environments can create


Security Issues significant governance and security issues.
Release
When all tests pass, the build is deployed to testing
environments for each stage in the release process

Cloud
Load Testing

Integration testing Staging


environment environment

3 Monitor + Learn

Automated functional Pre-production


testing environment environment
Monitor + Learn
Learn and understand how users use your app, how it reacts
and quickly fix issues and bugs
Plan the next iteration

Feedback

Monitor

4
Microsoft
Ecosystem People | Process | Tools

01
02
03
Develop

Developer Workstation
Build/CI
04

Build & Test


Release

Deploy
Team Foundation Server
Monitor

Monitor & Learn


Release Management Release Management
for Visual Studio for Visual Studio
Team Collaboration
Automation
Test
Service
Team Foundation Server
PowerShell | WAML Application Insights
Team Foundation Server
Azure
Resource
Microsoft Test Manager Management
xPlat Command Line

TFS DEV TEST QA

Workstations - On-Premises | Hybrid | Cloud Services - On-Premises | Hybrid | Cloud Environments - On-Premises | Hybrid | Cloud Monitoring - On-Premises | Hybrid | Cloud
Mixed
Ecosystem People | Process | Tools

01
02
03
Develop

Developer Workstation
Build/CI
04

Build & Test


Configuration

Deploy
Monitor

Monitor & Learn


Release
Team Collaboration

Test

This graphic shows OSS and partner products that are


integrated with the Microsoft DevOps solution
DevOps
1 Plan 4 Monitor + Learn

Development Production

2 Develop + Test 3 Release


© 2013 Microsoft Corporation. All rights reserved. Microsoft, 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.

You might also like