Change up everything
This commit is contained in:
Dirk Nederveen
parent
b8f616bf0f
commit
c8719a956a
GPG Key ID:
30C016E96E2219B8
229
index.html
229
index.html
|
|
@ -1,98 +1,118 @@
|
||||||
<!DOCTYPE html>
|
<!doctype html>
|
||||||
<html lang="en">
|
<html lang="en">
|
||||||
<head>
|
|
||||||
<meta charset="utf-8" />
|
<head>
|
||||||
<meta
|
<meta charset="utf-8">
|
||||||
name="viewport"
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
|
||||||
content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"
|
|
||||||
/>
|
|
||||||
|
|
||||||
<title>reveal.js</title>
|
<title>reveal.js</title>
|
||||||
|
|
||||||
<link rel="stylesheet" href="dist/reset.css" />
|
<link rel="stylesheet" href="dist/reset.css">
|
||||||
<link rel="stylesheet" href="dist/reveal.css" />
|
<link rel="stylesheet" href="dist/reveal.css">
|
||||||
<link rel="stylesheet" href="dist/theme/black.css" />
|
<link rel="stylesheet" href="dist/theme/black.css">
|
||||||
|
|
||||||
<!-- Theme used for syntax highlighted code -->
|
<!-- Theme used for syntax highlighted code -->
|
||||||
<link rel="stylesheet" href="plugin/highlight/monokai.css" />
|
<link rel="stylesheet" href="plugin/highlight/monokai.css">
|
||||||
</head>
|
</head>
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<div class="reveal">
|
<div class="reveal">
|
||||||
<div class="slides">
|
<div class="slides">
|
||||||
<section>
|
<section>
|
||||||
<section data-markdown>
|
<section data-markdown>
|
||||||
# About me * Dirk Nederveen,
|
# About me
|
||||||
[@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk) * Husband,
|
|
||||||
father of 3, Streaming Engineer (QA) @Jet-Stream * Interests: -
|
* Dirk Nederveen, [@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk)
|
||||||
Theology - Neurospychology - Reading - Beer brewing
|
* Husband, father of 3, Streaming Engineer (QA) @Jet-Stream
|
||||||
|
* Interests:
|
||||||
|
- Theology
|
||||||
|
- Neurospychology
|
||||||
|
- Reading
|
||||||
|
- Beer brewing
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<!-- <section id="toc">
|
<section data-markdown="" id="bluf">
|
||||||
<h1>TOC</h1>
|
# Why can't we deploy this today?
|
||||||
<ol style="list-style: lower-roman;">
|
</section>
|
||||||
<li><a href="#/deployment-anxiety-disorder">Deployment Anxiety Disorder</a></li>
|
|
||||||
<li><a href="#/feedback-latency">Feedback latency</a></li>
|
|
||||||
</ol>
|
|
||||||
</section> -->
|
|
||||||
|
|
||||||
<section id="deployment-anxiety-disorder">
|
|
||||||
<section>
|
<section>
|
||||||
<em> Please raise your hand if you ever... </em>
|
|
||||||
|
|
||||||
<ul>
|
|
||||||
<li class="fragment">
|
|
||||||
deployed code that you didn't trust
|
|
||||||
<span class="fragment"
|
|
||||||
>with a service disruption as a consequence 😱💥</span
|
|
||||||
>
|
|
||||||
</li>
|
|
||||||
<li class="fragment">
|
|
||||||
deployed code that you <em>did</em> trust
|
|
||||||
<span class="fragment">that did boom anyway 😱💥</span>
|
|
||||||
</li>
|
|
||||||
<li class="fragment">
|
|
||||||
worked with an acceptance/staging environment
|
|
||||||
<span class="fragment">and production still did boom 😱💥</span>
|
|
||||||
</li>
|
|
||||||
<li class="fragment">
|
|
||||||
held off a deployment on a Friday, to avoid '😱💥'
|
|
||||||
</li>
|
|
||||||
<li class="fragment">... on a Thursday</li>
|
|
||||||
</ul>
|
|
||||||
</section>
|
|
||||||
|
|
||||||
<section data-markdown>
|
<section data-markdown>
|
||||||
# Deployment Anxiety Disorder *A troublesome fear that prod go 💥.
|
# The story of a bug
|
||||||
Symptoms may include:* - excessive or insufficient release planning
|
|
||||||
- difficulty to perform updates - panic attacks - CYA strategies -
|
Starring:
|
||||||
entertaining thoughts about working at Hornbach
|
- 🦹🏻♂️ Customer
|
||||||
|
- 🦸🏼♂️ Support Hero
|
||||||
|
- 🧑💼 Product Owner
|
||||||
|
- 👩🏾💻 Sr. Dev
|
||||||
|
- 👷🏻♂️ Jr. Dev
|
||||||
|
- 👩🏼🚒 System Operator
|
||||||
</section>
|
</section>
|
||||||
<section data-markdown>
|
<section data-markdown>
|
||||||
# Stress hormones * natural response to stress * acute stress:
|
- 🦹🏻♂️ Customer calls with a question about sending an invoice on Monday 1 May, 🦸🏼♂️ Support Hero logs ticket BS-1234 in
|
||||||
adrenaline - fight-or-flight response - prepares your body for
|
Jira
|
||||||
action * prolonged stress: cortisol - freeze response - restlessness
|
- 🧑💼 Product Owner, 👩🏾💻 Sr. Dev and 🦸🏼♂️ Support Hero have triage meeting on Thursday 4 May, bug confirmed, priority
|
||||||
- anxiety disorders, depression * mortal enemy AND big ally - big
|
'Highest'
|
||||||
ally if you learn to regulate the body response to stress hormones
|
- 🧑💼 Product Owner and 👩🏾💻 Sr. Dev have backlog grooming meeting on Friday 5 May
|
||||||
|
- Team has Sprint Planning meeting on Monday 8 May, commit to BS-1234 for 2 Story Points
|
||||||
|
|
||||||
|
👇
|
||||||
|
</section>
|
||||||
|
<section data-markdown>
|
||||||
|
- 👷🏻♂️ Jr. Dev picks up BS-1234, needs clarification and sends 🦹🏻♂️ Customer an email on Wednesday 10 May
|
||||||
|
- 🦹🏻♂️ Customer responds Thursday 11 May, 16:00
|
||||||
|
- 👷🏻♂️ Jr. Dev starts implementation on Monday 15 May, opens PR #2345 in GitHub
|
||||||
|
- 👩🏾💻 Sr. Dev responds to PR #2345 on Tuesday 16 May 16:00, needs improvement
|
||||||
|
|
||||||
|
👇
|
||||||
|
</section>
|
||||||
|
<section data-markdown>
|
||||||
|
- 👷🏻♂️ Jr. Dev processes feedback on Thursday 18 May, 10:00
|
||||||
|
- 👩🏾💻 Sr. Dev merges PR #2345 on Thursday 18 May 🎉
|
||||||
|
- 👩🏼🚒 System Operator prepares release after Sprint end, and deploys update on Tuesday, 23 May
|
||||||
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section
|
<section>
|
||||||
data-markdown
|
<section data-markdown="">
|
||||||
style="font-family: 'Comic Sans', 'Comic Neue'"
|
# Value stream mapping
|
||||||
>
|
|
||||||
# Regulation 🏗️ * Respond to stress hormones for your benefit - from
|
- How the *value* flows through an organisation
|
||||||
*fight* to *take control* - from *flight* to *take a break* - from
|
- *Who* holds responsibility
|
||||||
*freeze* to *accept* * Apply brakes * Build trust * Control emotions
|
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section
|
<section data-markdown="">
|
||||||
data-markdown
|
* Delays in process
|
||||||
style="font-family: 'Comic Sans', 'Comic Neue'"
|
- Closed Sprint
|
||||||
>
|
- Asynchronous PR review
|
||||||
# Emotional regulation in software delivery 🏗️🏗️ * Apply brakes -
|
- Separate release team
|
||||||
Commit to an *acceptable* workload - Communicate about your needs *
|
* Hand-offs:
|
||||||
Build trust - Deliver quality software
|
- 🦸🏼♂️ Support Hero ➡️ Dev Team
|
||||||
|
- 👷🏻♂️ Jr. Dev ➡️ 👩🏾💻 Sr. Dev
|
||||||
|
- Dev Team ➡️ 👩🏼🚒 System Operator
|
||||||
|
</section>
|
||||||
|
|
||||||
|
<section data-markdown="">
|
||||||
|
# What to do this Monday?
|
||||||
|
|
||||||
|
* Sketch how a 1-hour bug streams through your org
|
||||||
|
- Discovery
|
||||||
|
- Selection/prioritisation
|
||||||
|
- Implementation
|
||||||
|
- Verification
|
||||||
|
- To production
|
||||||
|
</section>
|
||||||
|
</section>
|
||||||
|
|
||||||
|
<section>
|
||||||
|
<section data-markdown="">
|
||||||
|
# Processes are there for a reason!
|
||||||
|
|
||||||
|
but whom do they benefit?
|
||||||
|
</section>
|
||||||
|
|
||||||
|
<section data-markdown="">
|
||||||
|
# Closed sprint
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|
@ -100,60 +120,23 @@
|
||||||
<h1>Continuous delivery</h1>
|
<h1>Continuous delivery</h1>
|
||||||
|
|
||||||
<div style="width: 80%; float: left" data-markdown="">
|
<div style="width: 80%; float: left" data-markdown="">
|
||||||
* Build quality in * Work in small batches * Computers perform
|
* Build quality in
|
||||||
repetitive tasks, people solve problems * Relentlessly pursue
|
* Work in small batches
|
||||||
continuous improvement * Everyone is responsible
|
* Computers perform repetitive tasks, people solve problems
|
||||||
|
* Relentlessly pursue continuous improvement
|
||||||
|
* Everyone is responsible
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div style="float: right; width: 20%; height: 8em">
|
<div style="float: right; width: 20%; height: 8em">
|
||||||
<a href="https://www.bol.com/nl/nl/p/accelerate/9200000080652224">
|
<a href="https://www.bol.com/nl/nl/p/accelerate/9200000080652224">
|
||||||
<img src="accelerate.jpg" style="height: 50%" /> </a
|
<img src="accelerate.jpg" style="height: 50%;">
|
||||||
><br />
|
</a><br>
|
||||||
<a
|
<a href="https://www.informit.com/store/continuous-delivery-reliable-software-releases-through-9780321770424?ranMID=24808">
|
||||||
href="https://www.informit.com/store/continuous-delivery-reliable-software-releases-through-9780321770424?ranMID=24808"
|
<img src="cd-book.png" style="height: 50%;">
|
||||||
>
|
|
||||||
<img src="cd-book.png" style="height: 50%" />
|
|
||||||
</a>
|
</a>
|
||||||
</div>
|
</div>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section>
|
|
||||||
<section data-markdown>
|
|
||||||
# Value stream mapping How does the value stream through the
|
|
||||||
organisation? 👇
|
|
||||||
</section>
|
|
||||||
<section data-markdown>
|
|
||||||
- Customer calls with a question about sending an invoice on Monday
|
|
||||||
1 May, Support Hero logs ticket BS-1234 in Jira - Product Owner,
|
|
||||||
Tech Lead and Support Hero have triage meeting on Thursday 4 May,
|
|
||||||
bug confirmed, priority 'Highest' - Product Owner and Tech Lead have
|
|
||||||
backlog grooming meeting on Friday 5 May - Team has Sprint Planning
|
|
||||||
meeting on Monday 8 May, commit to BS-1234 for 2 Story Points 👇
|
|
||||||
</section>
|
|
||||||
<section data-markdown>
|
|
||||||
- Jr. Dev picks up BS-1234, needs clarification and sends Customer
|
|
||||||
an email on Wednesday 10 May - Customer responds Thursday 11 May,
|
|
||||||
16:00 - Jr. Dev starts implementation on Monday 15 May, opens PR
|
|
||||||
#2345 in GitHub - Sr. Dev responds to PR #2345 on Tuesday 16 May
|
|
||||||
16:00, needs improvement 👇
|
|
||||||
</section>
|
|
||||||
<section data-markdown>
|
|
||||||
- Jr. Dev processes feedback on Thursday 18 May, 10:00 - Sr. Dev
|
|
||||||
merges PR #2345 on Thursday 18 May 🎉 - Operations Team prepares
|
|
||||||
release after Sprint end, and deploys update on Tuesday, 23 May
|
|
||||||
</section>
|
|
||||||
|
|
||||||
<section data-markdown="">
|
|
||||||
Why is this process slow? * Closed Sprint (1 week) * Hand-offs: -
|
|
||||||
Support Hero ➡️ Tech Team - Jr. Dev ➡️ Sr. Dev - Dev Team ➡️ Ops
|
|
||||||
team * Delays in process - Asynchronous PR review - Separate release
|
|
||||||
team
|
|
||||||
</section>
|
|
||||||
|
|
||||||
<section data-markdown="">
|
|
||||||
# What to do this Monday? * Draw the value stream in your org *
|
|
||||||
</section>
|
|
||||||
</section>
|
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|
@ -169,13 +152,13 @@
|
||||||
hash: true,
|
hash: true,
|
||||||
|
|
||||||
// Learn about plugins: https://revealjs.com/plugins/
|
// Learn about plugins: https://revealjs.com/plugins/
|
||||||
plugins: [RevealMarkdown, RevealHighlight, RevealNotes],
|
plugins: [RevealMarkdown, RevealHighlight, RevealNotes]
|
||||||
});
|
});
|
||||||
</script>
|
</script>
|
||||||
<script>
|
<script>
|
||||||
document
|
document.querySelectorAll('.slides section a[href^="http"]').
|
||||||
.querySelectorAll('.slides section a[href^="http"]')
|
forEach(a => a.setAttribute('target', '_blank'))
|
||||||
.forEach((a) => a.setAttribute("target", "_blank"));
|
|
||||||
</script>
|
</script>
|
||||||
</body>
|
</body>
|
||||||
|
|
||||||
</html>
|
</html>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue