0% found this document useful (0 votes)
9 views35 pages

Devops Intro For Pms

The document presents an introduction to DevOps for project managers, emphasizing its significance in software delivery and IT change management. It outlines key principles, practices, and the importance of a high-performance culture, automation, and continuous improvement in achieving enterprise agility. The training aims to equip project managers with the knowledge to implement DevOps effectively within their organizations.

Uploaded by

ashish kher
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views35 pages

Devops Intro For Pms

The document presents an introduction to DevOps for project managers, emphasizing its significance in software delivery and IT change management. It outlines key principles, practices, and the importance of a high-performance culture, automation, and continuous improvement in achieving enterprise agility. The training aims to equip project managers with the knowledge to implement DevOps effectively within their organizations.

Uploaded by

ashish kher
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 35

Hello.

ASPE & Techtown Training


An Introduction to DevOps for
Project Managers

Today’s Presenters :
• Chris Knotts, PMP – Enterprise training curriculum director: DevOps,
emerging technologies, & technology innovation
• Robert Knapp – ASPE corporate training advisor
2016 DevOps Market Vision

Welcome! We will examine:


• A bit of history
• Getting past DevOps as a buzzword and getting to
the real implications for project managers
• A typical enterprise environment and the life
cycle of IT and software delivery projects
• Enterprise agility as a bridge to DevOps
• The relationship between continuous delivery,
incremental workflows, and DevOps training
Some assumptions for our time
together:
• DevOps practices are most powerful when applied
to contexts of software delivery and IT change
management
• DevOps, by definition, is never a “one-size-fits-all”
remedy
• DevOps is about drilling down on your own
organization’s specific problems and challenges
2013: The Phoenix Project:
A Novel About IT, DevOps, and Helping Your Business Win

Gene Kim

Kevin Behr

George
Spafford
2015 Puppet “State of DevOps” Report
executive summary:
• High-performing IT organizations: 1) deploy 30x more
frequently 2) have 200x shorter lead times 3) have 60x fewer
failures and recover 168x faster.
• Lean management and continuous delivery practices create
conditions to deliver value faster, sustainably.
• High performance is achievable whether your applications are
greenfield, brownfield or legacy.
• IT managers play a critical role in any DevOps transformation.
• Diversity matters.
• Deployment pain is a key indicator of IT performance.
• Burnout can be prevented, and DevOps can help.
Today’s enterprise IT looks like this.
A simplified look at the enterprise
Change Management

Application IT Operations, Production


Development teams Environments, Support

Business Customer

S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e
A simplified look at the enterprise
The business! (different departments, needs, stakeholders etc.)

The triumphant Agile team! IT


O Operations!!
p
e
r
a
t
Deploy i
o
D
& nSa
Support &
et
Sca
y
su
t
er
m
s
i
t
y
Customers / end users!!
A simplified look at the enterprise
Change Management

Application IT Operations, Production


Development teams Environments, Support

Business Customer

S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e
Increasing quality in software and IT
delivery as a product of work
Application Delivery & Cost of Defects

50% of defects introduced


here
2011: Continuous Delivery:
Reliable Software Releases Through Build, Test, &
Deployment Automation

Jez Humble

Dave Farley
Welcome to the 21st century!
A simplified
A simplifiedlook
lookat
atthe enterprise
an enterprise
The deployment
pipeline concept

Source: Continuous Delivery: Reliable


Software Releases through Build, Test,
and Deployment Automation
Test automation
What is DevOps Really?
What is DevOps?
Take 1 of 3:
What is DevOps?
Take 2 of 3:
The fundamental principles of DevOps as generally agreed
upon by the most influential early members of the DevOps
community, were summed up in the acronym “CAMS.”

CAMS
• Culture
• Automation
• Measurement
• Sharing
What is DevOps?
Take 2 of 3:
Jez Humble later suggested adding an “L” to the
acronym, changing it to “CALMS.” We endorse and
encourage this addition!
Jez Humble

CALMS
• Culture
• Automation
• Lean
• Measurement
• Sharing
What is DevOps?
Take 3 of 3: “From the ah-ha to the ka-ching”
Concept / ideation
Value

DevOps is not about IT problems: DevOps is about


business problems.
What is DevOps?
Attribute Key Elements

High-trust, high- Unified mission; aligned incentives across departments and


performance culture teams; little fear/failure/blame, high quality of work life

IT capabilities = strategic Projects, features and work flow through fast cycles times,
assets, not cost centers systems are “anti-fragile,” IT processes & capabilities are aligned
with overarching organizational needs
Highly automated
processes; mature Technical phases of projects supported by common tools and
deployment pipeline automation processes, collaboration replaces handoffs,
codebase/IT infrastructure is agile and functional by default
Continuous delivery of
software and IT value Features, projects and IT work follow a regular, iterative flow.
Cycle time is short, workflow favors small frequent changes
Commitment to
continuous learning Disciplined feedback loops quickly travel back upstream for
& improvement inclusion. Tools for monitoring, measurement and alerting
implemented & effective. Shared knowledge repositories.
Continuous Delivery Maturity Matrix
How can we get more specific about applying
DevOps principles for our own work?
Common goals of an enterprise DevOps practice
• Increased deployment frequency
• Reduced lead time for changes
• Faster recovery when problems occur
• More robust and better integrated security
• A “shift left” in quality – quality of code, testing,
architecture, “deployability” and culture
• Fast feedback loops and effective communication
between teams and departments
Obvious (and important) implications
for project managers…
Plan-driven corporate behavior
Equalizing Requirements
One of the most important tools of
DevOps: Failure
Getting from: To:

Failure is not a cause for blame, it is a vehicle for change,


learning, and improvement.
The “Agile Triangle”

Source: Jim Highsmith, Agile Project Management (2nd Edition)


Jason Bloomberg, Intellyx

http://insights.wired.com/profiles/blogs/the-devops-drumbeat-rethinking-the-iron-triangle#axzz42wCYG2EG
Jason Bloomberg’s Agile
Architecture “Quality Star”
Jason Bloomberg’s Agile
Architecture “Quality Star”
To sum up:
• Stakeholders are oriented around teams and projects
• Quality is tied to value – and is everyone’s responsibility,
from requirements and code creation to deployment
• Technical non-functional requirements (and technical
debt) receive equal priority to functional requirements
• Deliver often, deliver early, learn and adapt. Roll planning
into your continuous processes
• Testing and QA is not a separate function: it is a key
enabler of continuous delivery
• Expect failure and plan for the contingency
People, teams, technology,
processes and value
Thank you!

You might also like