maurobaraldi/devops-culture.html

## devops-culture.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8" />
    <meta name="keywords" content="remark,remarkjs,markdown,slideshow,presentation" />
    <meta name="description" content="A simple, in-browser, markdown-driven slideshow tool." />
    <title>DevOps Culture & Initiative Overview</title>
    <style>
      @import url(https://fonts.googleapis.com/css?family=Droid+Serif);
      @import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
      @import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);

      body {
        font-family: 'Droid Serif';
      }
      h1, h2, h3 {
        font-family: 'Yanone Kaffeesatz';
        font-weight: 400;
        margin-bottom: 0;
      }
      .remark-slide-content h1 { font-size: 3em; }
      .remark-slide-content h2 { font-size: 2em; }
      .remark-slide-content h3 { font-size: 1.6em; }
      .footnote {
        position: absolute;
        bottom: 3em;
      }
      li p { line-height: 1.25em; }
      .red { color: #fa0000; }
      .large { font-size: 2em; }
      a, a > code {
        color: rgb(249, 38, 114);
        text-decoration: none;
      }
      code {
        background: #e7e8e2;
        border-radius: 5px;
      }
      .remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }
      .remark-code-line-highlighted     { background-color: #373832; }
      .pull-left {
        float: left;
        width: 47%;
      }
      .pull-right {
        float: right;
        width: 47%;
      }
      .pull-right ~ p {
        clear: both;
      }
      #slideshow .slide .content {
        padding: 1em 3em;
        background: url(kuehne-nagel-logo.png) no-repeat top right;
      }
      #slideshow .slide .content code {
        font-size: 0.8em;
      }
      #slideshow .slide .content pre code {
        font-size: 0.9em;
        padding: 15px;
      }

      .inverse {
        background: #272822;
        color: #777872;
        text-shadow: 0 0 20px #333;
      }
      .inverse h1, .inverse h2 {
        color: #f3f3f3;
        line-height: 0.8em;
      }

      /* Slide-specific styling */
      #slide-inverse .footnote {
        bottom: 12px;
        left: 20px;
      }
      #slide-how .slides {
        font-size: 0.9em;
        position: absolute;
        top:  151px;
        right: 140px;
      }
      #slide-how .slides h3 {
        margin-top: 0.2em;
      }
      #slide-how .slides .first, #slide-how .slides .second {
        padding: 1px 20px;
        height: 90px;
        width: 120px;
        -moz-box-shadow: 0 0 10px #777;
        -webkit-box-shadow: 0 0 10px #777;
        box-shadow: 0 0 10px #777;
      }
      #slide-how .slides .first {
        background: #fff;
        position: absolute;
        top: 20%;
        left: 20%;
        z-index: 1;
      }
      #slide-how .slides .second {
        position: relative;
        background: #fff;
        z-index: 0;
      }

      /* Two-column layout */
      .left-column {
        color: #777;
        width: 20%;
        height: 92%;
        float: left;
      }
        .left-column h2:last-of-type, .left-column h3:last-child {
          color: #000;
        }
      .right-column {
        width: 75%;
        float: right;
        padding-top: 1em;
      }
    </style>
  </head>
  <body>
    <textarea id="source">
name: inverse
layout: true
class: center, middle, inverse
---
## DevOps Culture & Initiative Overview

A practical guide for Product, Business, Development, QA and Management

.footnote[This presentation is available [here](https://gist.github.com/maurobaraldi/e63a8bf49ec9f86ad4f43a3933eac264)]
---
layout: false
.left-column[
  ## Agenda
]
.right-column[

- What is DevOps?

- How it impacts the Business

- Core principles and culture

- DevOps lifecycle and practices

- What DevOps means for each role

- Metrics to Track in DevOps

- Our DevOps initiative and roadmap

- Next steps
]
---
template: inverse

## What is DevOps and why does it matter?

<!-- <img src="octopus-devops-infinity-small.png" /> -->
<img src="https://www.parasoft.com/wp-content/uploads/2025/07/1-DevOps-Continuous-Testing-Infinity-Loop.png" />
---
.left-column[
  ## What is DevOps?
]
.right-column[
- A culture and way of working, not just tools

- Brings Development and Operations together

- Focus on collaboration, automation, and continuous improvement

- Goal: deliver value to customers faster, safer, and more reliably

- Emphasizes shared responsibility for the entire delivery lifecycle
]
---
template: inverse

## How it impacts the Business?
---
.left-column[
  ## How it impacts the Business
]
.right-column[
- Faster time‑to‑market for features and products

- Higher product quality and stability

- Reduced operational risk and outages

- Better alignment between business goals and technology delivery

- Improved customer satisfaction and retention
]
---
template: inverse

## Core principles and culture
---
.left-column[
  ## Core principles and culture
]
.right-column[
- Collaboration across teams

- Automation wherever practical

- Continuous integration and continuous delivery (CI/CD)

- Monitoring and feedback loops

- Shared responsibility for outcomes

- Embracing failure as a learning opportunity
]
---
template: inverse

## DevOps Culture
---
.left-column[
  ## DevOps Culture
]
.right-column[
- Blameless problem solving

- Transparency and communication

- Learning from failures

- Empowering teams to own delivery end‑to‑end

- Focus on value, not only activities
]
---
template: inverse

## DevOps lifecycle
---
.left-column[
  ## DevOps lifecycle
]
.right-column[
- Plan → Code → Build → Test → Release → Deploy → Operate → Monitor

- Feedback loops connect every stage

- Small, frequent changes instead of big releases
]
---
.left-column[
  ## Core DevOps Practices
]
.right-column[
- Version control for everything (code, configuration, scripts)

- Automated builds and tests

- Continuous Integration and Continuous Delivery pipelines

- Infrastructure as Code

- Automated monitoring and alerting
]
---
.left-column[
  ## DevOps Tooling – High Level
]
.right-column[
- Source control systems

- Build and CI/CD platforms

- Test automation frameworks

- Cloud and infrastructure provisioning tools

- Monitoring and logging platforms

- Collaboration and knowledge sharing tools
]
---
template: inverse

## What DevOps means for each role
---
.left-column[
  ## DevOps for POs and BAs
]
.right-column[
- Faster validation of ideas through quicker releases

- Clear visibility into delivery progress

- Better collaboration with technical teams

- Ability to reprioritize based on real user feedback
]
---
.left-column[
  ## DevOps for Developers
]
.right-column[
- More autonomy over build and deployment

- Rapid feedback from automated tests and monitoring

- Greater ownership of code in production

- Less manual, repetitive work through automation
]
---
.left-column[
  ## DevOps for QA and Testers
]
.right-column[
- Shift‑left testing: quality built in from the start

- Increased use of automated testing

- Earlier involvement in design and development

- Shared responsibility for product quality
]
---
.left-column[
  ## DevOps for Managers
]
.right-column[
- Higher team productivity and engagement

- Data‑driven insight into delivery performance

- Reduced risk through smaller, controlled releases

- Improved alignment between strategy and execution
]
---
template: inverse

## Metrics to Track in DevOps
---
.left-column[
  ## Measuring What Matters
]
.right-column[
- Deployment Frequency: How often we successfully release to production

- Lead Time for Change: Time from code commit to production

- Change Failure Rate: % of releases causing incidents or rollbacks

- Mean Time to Recovery (MTTR):Time to restore service after failure

- Business Impact: Customer satisfaction, reliability, performance trends
]
---
.left-column[
  ## KPI Dashboard – Executive View
]
.right-column[
- Flow Metrics: deployment frequency, lead time, cycle time

- Stability Metrics: change failure rate, MTTR, incident trends

- Pipeline Health: build success rate, automated test coverage

- Reliability: availability %, SLA/SLO compliance, error rate

- Automation Level: % automated deployments and infrastructure as code

- Self-Service Adoption: environment provisioning usage across teams

- Customer Experience: latency, uptime, user feedback score
]
---
template: inverse

## Our DevOps initiative and roadmap
---
.left-column[
  ## What We Are Doing
]
.right-column[
- Building CI/CD pipelines for core products

- Expanding automated testing coverage

- Implementing Infrastructure as Code

- Implementing monitoring and observability

- Encouraging cross‑functional collaboration
]
---
.left-column[
  ## Roadmap
]
.right-column[
- Short term: standardize tooling and processes

- Mid term: automate builds, tests, and deployments

- Long term: self‑service environments and full observability

- Continuous improvement throughout
]
---
.left-column[
  ## How to contribute and get involved
]
.right-column[
- Be open to collaboration across roles

- Embrace automation and standardization

- Share knowledge and lessons learned

- Focus on customer value and outcomes

- Adopt shared ownership of self-service environments rather than relying on a single DevOps role
]
---
.left-column[
  ## Continuous improvement
]
.right-column[
- Identify pilot projects

- Define measurable goals

- Provide training and enablement

- Review progress regularly

- Provide feedback and iterate on processes
]
---
name: last-page
template: inverse

## That's all folks (for now)!

Slideshow created using [remark](http://github.com/gnab/remark).
    </textarea>
    <script src="https://remarkjs.com/downloads/remark-latest.min.js"></script>
    <script>
      var hljs = remark.highlighter.engine;
    </script>
    <script src="remark.language.js"></script>
    <script>
      var slideshow = remark.create({
          highlightStyle: 'monokai',
          highlightLanguage: 'remark',
          highlightLines: true
        }) ;
    </script>
    <script>
      var _gaq = _gaq || [];
      _gaq.push(['_setAccount', 'UA-44561333-1']);
      _gaq.push(['_trackPageview']);

      (function() {
        var ga = document.createElement('script');
        ga.src = 'https://ssl.google-analytics.com/ga.js';
        var s = document.scripts[0];
        s.parentNode.insertBefore(ga, s);
      }());
    </script>
  </body>
</html>
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8" />
	<meta name="keywords" content="remark,remarkjs,markdown,slideshow,presentation" />
	<meta name="description" content="A simple, in-browser, markdown-driven slideshow tool." />
	<title>DevOps Culture & Initiative Overview</title>
	<style>
	@import url(https://fonts.googleapis.com/css?family=Droid+Serif);
	@import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
	@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);

	body {
	font-family: 'Droid Serif';
	}
	h1, h2, h3 {
	font-family: 'Yanone Kaffeesatz';
	font-weight: 400;
	margin-bottom: 0;
	}
	.remark-slide-content h1 { font-size: 3em; }
	.remark-slide-content h2 { font-size: 2em; }
	.remark-slide-content h3 { font-size: 1.6em; }
	.footnote {
	position: absolute;
	bottom: 3em;
	}
	li p { line-height: 1.25em; }
	.red { color: #fa0000; }
	.large { font-size: 2em; }
	a, a > code {
	color: rgb(249, 38, 114);
	text-decoration: none;
	}
	code {
	background: #e7e8e2;
	border-radius: 5px;
	}
	.remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }
	.remark-code-line-highlighted { background-color: #373832; }
	.pull-left {
	float: left;
	width: 47%;
	}
	.pull-right {
	float: right;
	width: 47%;
	}
	.pull-right ~ p {
	clear: both;
	}
	#slideshow .slide .content {
	padding: 1em 3em;
	background: url(kuehne-nagel-logo.png) no-repeat top right;
	}
	#slideshow .slide .content code {
	font-size: 0.8em;
	}
	#slideshow .slide .content pre code {
	font-size: 0.9em;
	padding: 15px;
	}

	.inverse {
	background: #272822;
	color: #777872;
	text-shadow: 0 0 20px #333;
	}
	.inverse h1, .inverse h2 {
	color: #f3f3f3;
	line-height: 0.8em;
	}

	/* Slide-specific styling */
	#slide-inverse .footnote {
	bottom: 12px;
	left: 20px;
	}
	#slide-how .slides {
	font-size: 0.9em;
	position: absolute;
	top: 151px;
	right: 140px;
	}
	#slide-how .slides h3 {
	margin-top: 0.2em;
	}
	#slide-how .slides .first, #slide-how .slides .second {
	padding: 1px 20px;
	height: 90px;
	width: 120px;
	-moz-box-shadow: 0 0 10px #777;
	-webkit-box-shadow: 0 0 10px #777;
	box-shadow: 0 0 10px #777;
	}
	#slide-how .slides .first {
	background: #fff;
	position: absolute;
	top: 20%;
	left: 20%;
	z-index: 1;
	}
	#slide-how .slides .second {
	position: relative;
	background: #fff;
	z-index: 0;
	}

	/* Two-column layout */
	.left-column {
	color: #777;
	width: 20%;
	height: 92%;
	float: left;
	}
	.left-column h2:last-of-type, .left-column h3:last-child {
	color: #000;
	}
	.right-column {
	width: 75%;
	float: right;
	padding-top: 1em;
	}
	</style>
	</head>
	<body>
	<textarea id="source">
	name: inverse
	layout: true
	class: center, middle, inverse
	---
	## DevOps Culture & Initiative Overview

	A practical guide for Product, Business, Development, QA and Management

	.footnote[This presentation is available [here](https://gist.github.com/maurobaraldi/e63a8bf49ec9f86ad4f43a3933eac264)]
	---
	layout: false
	.left-column[
	## Agenda
	]
	.right-column[

	- What is DevOps?

	- How it impacts the Business

	- Core principles and culture

	- DevOps lifecycle and practices

	- What DevOps means for each role

	- Metrics to Track in DevOps

	- Our DevOps initiative and roadmap

	- Next steps
	]
	---
	template: inverse

	## What is DevOps and why does it matter?

	<!-- <img src="octopus-devops-infinity-small.png" /> -->
	<img src="https://www.parasoft.com/wp-content/uploads/2025/07/1-DevOps-Continuous-Testing-Infinity-Loop.png" />
	---
	.left-column[
	## What is DevOps?
	]
	.right-column[
	- A culture and way of working, not just tools

	- Brings Development and Operations together

	- Focus on collaboration, automation, and continuous improvement

	- Goal: deliver value to customers faster, safer, and more reliably

	- Emphasizes shared responsibility for the entire delivery lifecycle
	]
	---
	template: inverse

	## How it impacts the Business?
	---
	.left-column[
	## How it impacts the Business
	]
	.right-column[
	- Faster time‑to‑market for features and products

	- Higher product quality and stability

	- Reduced operational risk and outages

	- Better alignment between business goals and technology delivery

	- Improved customer satisfaction and retention
	]
	---
	template: inverse

	## Core principles and culture
	---
	.left-column[
	## Core principles and culture
	]
	.right-column[
	- Collaboration across teams

	- Automation wherever practical

	- Continuous integration and continuous delivery (CI/CD)

	- Monitoring and feedback loops

	- Shared responsibility for outcomes

	- Embracing failure as a learning opportunity
	]
	---
	template: inverse

	## DevOps Culture
	---
	.left-column[
	## DevOps Culture
	]
	.right-column[
	- Blameless problem solving

	- Transparency and communication

	- Learning from failures

	- Empowering teams to own delivery end‑to‑end

	- Focus on value, not only activities
	]
	---
	template: inverse

	## DevOps lifecycle
	---
	.left-column[
	## DevOps lifecycle
	]
	.right-column[
	- Plan → Code → Build → Test → Release → Deploy → Operate → Monitor

	- Feedback loops connect every stage

	- Small, frequent changes instead of big releases
	]
	---
	.left-column[
	## Core DevOps Practices
	]
	.right-column[
	- Version control for everything (code, configuration, scripts)

	- Automated builds and tests

	- Continuous Integration and Continuous Delivery pipelines

	- Infrastructure as Code

	- Automated monitoring and alerting
	]
	---
	.left-column[
	## DevOps Tooling – High Level
	]
	.right-column[
	- Source control systems

	- Build and CI/CD platforms

	- Test automation frameworks

	- Cloud and infrastructure provisioning tools

	- Monitoring and logging platforms

	- Collaboration and knowledge sharing tools
	]
	---
	template: inverse

	## What DevOps means for each role
	---
	.left-column[
	## DevOps for POs and BAs
	]
	.right-column[
	- Faster validation of ideas through quicker releases

	- Clear visibility into delivery progress

	- Better collaboration with technical teams

	- Ability to reprioritize based on real user feedback
	]
	---
	.left-column[
	## DevOps for Developers
	]
	.right-column[
	- More autonomy over build and deployment

	- Rapid feedback from automated tests and monitoring

	- Greater ownership of code in production

	- Less manual, repetitive work through automation
	]
	---
	.left-column[
	## DevOps for QA and Testers
	]
	.right-column[
	- Shift‑left testing: quality built in from the start

	- Increased use of automated testing

	- Earlier involvement in design and development

	- Shared responsibility for product quality
	]
	---
	.left-column[
	## DevOps for Managers
	]
	.right-column[
	- Higher team productivity and engagement

	- Data‑driven insight into delivery performance

	- Reduced risk through smaller, controlled releases

	- Improved alignment between strategy and execution
	]
	---
	template: inverse

	## Metrics to Track in DevOps
	---
	.left-column[
	## Measuring What Matters
	]
	.right-column[
	- Deployment Frequency: How often we successfully release to production

	- Lead Time for Change: Time from code commit to production

	- Change Failure Rate: % of releases causing incidents or rollbacks

	- Mean Time to Recovery (MTTR):Time to restore service after failure

	- Business Impact: Customer satisfaction, reliability, performance trends
	]
	---
	.left-column[
	## KPI Dashboard – Executive View
	]
	.right-column[
	- Flow Metrics: deployment frequency, lead time, cycle time

	- Stability Metrics: change failure rate, MTTR, incident trends

	- Pipeline Health: build success rate, automated test coverage

	- Reliability: availability %, SLA/SLO compliance, error rate

	- Automation Level: % automated deployments and infrastructure as code

	- Self-Service Adoption: environment provisioning usage across teams

	- Customer Experience: latency, uptime, user feedback score
	]
	---
	template: inverse

	## Our DevOps initiative and roadmap
	---
	.left-column[
	## What We Are Doing
	]
	.right-column[
	- Building CI/CD pipelines for core products

	- Expanding automated testing coverage

	- Implementing Infrastructure as Code

	- Implementing monitoring and observability

	- Encouraging cross‑functional collaboration
	]
	---
	.left-column[
	## Roadmap
	]
	.right-column[
	- Short term: standardize tooling and processes

	- Mid term: automate builds, tests, and deployments

	- Long term: self‑service environments and full observability

	- Continuous improvement throughout
	]
	---
	.left-column[
	## How to contribute and get involved
	]
	.right-column[
	- Be open to collaboration across roles

	- Embrace automation and standardization

	- Share knowledge and lessons learned

	- Focus on customer value and outcomes

	- Adopt shared ownership of self-service environments rather than relying on a single DevOps role
	]
	---
	.left-column[
	## Continuous improvement
	]
	.right-column[
	- Identify pilot projects

	- Define measurable goals

	- Provide training and enablement

	- Review progress regularly

	- Provide feedback and iterate on processes
	]
	---
	name: last-page
	template: inverse

	## That's all folks (for now)!

	Slideshow created using [remark](http://github.com/gnab/remark).
	</textarea>
	<script src="https://remarkjs.com/downloads/remark-latest.min.js"></script>
	<script>
	var hljs = remark.highlighter.engine;
	</script>
	<script src="remark.language.js"></script>
	<script>
	var slideshow = remark.create({
	highlightStyle: 'monokai',
	highlightLanguage: 'remark',
	highlightLines: true
	}) ;
	</script>
	<script>
	var _gaq = _gaq \|\| [];
	_gaq.push(['_setAccount', 'UA-44561333-1']);
	_gaq.push(['_trackPageview']);

	(function() {
	var ga = document.createElement('script');
	ga.src = 'https://ssl.google-analytics.com/ga.js';
	var s = document.scripts[0];
	s.parentNode.insertBefore(ga, s);
	}());
	</script>
	</body>
	</html>
No results found