From c8719a956a3a6a8f3891171a2fba0938253f57b5 Mon Sep 17 00:00:00 2001 From: Dirk Nederveen Date: Tue, 23 May 2023 20:51:40 +0200 Subject: [PATCH] Change up everything --- index.html | 309 +++++++++++++++++++++++++---------------------------- 1 file changed, 146 insertions(+), 163 deletions(-) diff --git a/index.html b/index.html index b8923bcb..8c08dc47 100644 --- a/index.html +++ b/index.html @@ -1,181 +1,164 @@ - + - - - - reveal.js + + + - - - + reveal.js - - - + + + - -
-
-
-
- # About me * Dirk Nederveen, - [@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk) * Husband, - father of 3, Streaming Engineer (QA) @Jet-Stream * Interests: - - Theology - Neurospychology - Reading - Beer brewing -
+ + + + + +
+
+
+
+ # About me + + * Dirk Nederveen, [@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk) + * Husband, father of 3, Streaming Engineer (QA) @Jet-Stream + * Interests: + - Theology + - Neurospychology + - Reading + - Beer brewing +
+
+ +
+ # Why can't we deploy this today? +
+ +
+
+ # The story of a bug + + Starring: + - 🦹🏻‍♂️ Customer + - 🦸🏼‍♂️ Support Hero + - 🧑‍💼 Product Owner + - 👩🏾‍💻 Sr. Dev + - 👷🏻‍♂️ Jr. Dev + - 👩🏼‍🚒 System Operator +
+
+ - 🦹🏻‍♂️ Customer calls with a question about sending an invoice on Monday 1 May, 🦸🏼‍♂️ Support Hero logs ticket BS-1234 in + Jira + - 🧑‍💼 Product Owner, 👩🏾‍💻 Sr. Dev and 🦸🏼‍♂️ Support Hero have triage meeting on Thursday 4 May, bug confirmed, priority + 'Highest' + - 🧑‍💼 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 + + 👇 +
+
+ - 👷🏻‍♂️ 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 + + 👇 +
+
+ - 👷🏻‍♂️ 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 +
+
+ +
+
+ # Value stream mapping + + - How the *value* flows through an organisation + - *Who* holds responsibility
- - -
-
- Please raise your hand if you ever... - -
    -
  • - deployed code that you didn't trust - with a service disruption as a consequence 😱💥 -
    • -
  • - deployed code that you did trust - that did boom anyway 😱💥 -
    • -
  • - worked with an acceptance/staging environment - and production still did boom 😱💥 -
    • -
  • - held off a deployment on a Friday, to avoid '😱💥' -
    • -
  • ... on a Thursday
    • -
-
- -
- # Deployment Anxiety Disorder *A troublesome fear that prod go 💥. - Symptoms may include:* - excessive or insufficient release planning - - difficulty to perform updates - panic attacks - CYA strategies - - entertaining thoughts about working at Hornbach -
-
- # Stress hormones * natural response to stress * acute stress: - adrenaline - fight-or-flight response - prepares your body for - action * prolonged stress: cortisol - freeze response - restlessness - - anxiety disorders, depression * mortal enemy AND big ally - big - ally if you learn to regulate the body response to stress hormones -
- -
- # Regulation 🏗️ * Respond to stress hormones for your benefit - from - *fight* to *take control* - from *flight* to *take a break* - from - *freeze* to *accept* * Apply brakes * Build trust * Control emotions -
- -
- # Emotional regulation in software delivery 🏗️🏗️ * Apply brakes - - Commit to an *acceptable* workload - Communicate about your needs * - Build trust - Deliver quality software -
+
+ * Delays in process + - Closed Sprint + - Asynchronous PR review + - Separate release team + * Hand-offs: + - 🦸🏼‍♂️ Support Hero ➡️ Dev Team + - 👷🏻‍♂️ Jr. Dev ➡️ 👩🏾‍💻 Sr. Dev + - Dev Team ➡️ 👩🏼‍🚒 System Operator
-
-

Continuous delivery

+
+ # What to do this Monday? -
- * Build quality in * Work in small batches * Computers perform - repetitive tasks, people solve problems * Relentlessly pursue - continuous improvement * Everyone is responsible -
+ * Sketch how a 1-hour bug streams through your org + - Discovery + - Selection/prioritisation + - Implementation + - Verification + - To production +
+
- +
+
+ # Processes are there for a reason! + + but whom do they benefit?
-
-
- # Value stream mapping How does the value stream through the - organisation? 👇 -
-
- - 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 👇 -
-
- - 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 👇 -
-
- - 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 -
- -
- 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 -
- -
- # What to do this Monday? * Draw the value stream in your org * -
+
+ # Closed sprint
-
+
+ +
+

Continuous delivery

+ +
+ * Build quality in + * Work in small batches + * Computers perform repetitive tasks, people solve problems + * Relentlessly pursue continuous improvement + * Everyone is responsible +
+ +
+ + +
+ + + +
+
+
+
- - - - - + + + + + + - // Learn about plugins: https://revealjs.com/plugins/ - plugins: [RevealMarkdown, RevealHighlight, RevealNotes], - }); - - -