Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood
Devops intro
1. 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
2. 2016 DevOps Market Vision
• 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
Welcome! We will examine:
3. 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
4. 2013: The Phoenix Project:
A Novel About IT, DevOps, and Helping Your Business Win
Gene Kim
George
Spafford
Kevin Behr
5. 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.
8. A simplified look at the enterprise
s
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
Business Customer
Application
Development teams
IT Operations, Production
Environments, Support
Change Management
10. The triumphant Agile team! IT Operations!!
The business! (different departments, needs, stakeholders etc.)
Customers / end users!!
Deploy & Support
11. A simplified look at the enterprise
s
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
Business Customer
Application
Development teams
IT Operations, Production
Environments, Support
Change Management
12. 50% of defects introduced
here
Increasing quality in software and IT
delivery as a product of work
Application Delivery & Cost of Defects
19. 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:
20. CALMS
• Culture
• Automation
• Lean
• Measurement
• Sharing
Jez Humble later suggested adding an “L” to the
acronym, changing it to “CALMS.” We endorse
and encourage this addition!
Jez Humble
What is DevOps?
Take 2 of 3:
21. What is DevOps?
Take 3 of 3: “From the ah-ha to the ka-ching”
DevOps is not about IT problems: DevOps is about
business problems.
Concept / ideation
Value
22. Attribute Key Elements
High-trust, high-
performance culture
IT capabilities = strategic
assets, not cost centers
Highly automated
processes; mature
deployment pipeline
Continuous delivery of
software and IT value
Commitment to
continuous learning
& improvement
Unified mission; aligned incentives across departments and
teams; little fear/failure/blame, high quality of work life
Projects, features and work flow through fast cycles times,
systems are “anti-fragile,” IT processes & capabilities are aligned
with overarching organizational needs
Technical phases of projects supported by common tools and
automation processes, collaboration replaces handoffs,
codebase/IT infrastructure is agile and functional by default
Features, projects and IT work follow a regular, iterative flow.
Cycle time is short, workflow favors small frequent changes
Disciplined feedback loops quickly travel back upstream for
inclusion. Tools for monitoring, measurement and alerting
implemented & effective. Shared knowledge repositories.
What is DevOps?
24. 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
28. 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.
33. 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
