# Why can't we deploy this today?
# 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

🦹🏻‍♂️
🦸🏼‍♂️
🧑‍💼
👩🏾‍💻 👷🏻‍♂️
👩🏼‍🚒

The story of a bug

1 May: 🦹🏻‍♂️ →📞→ 🦸🏼‍♂️
4 May: 🧑‍💼 👩🏾‍💻 🦸🏼‍♂️ → 🐛
5 May: 🧑‍💼 👩🏾‍💻
8 May: 🧑‍💼​ 🦸🏼‍♂️ 👩🏾‍💻 👷🏻‍♂️

# Closed sprint - Two weeks is fast in context of 6 month CD-ROM releases! - How long does shipping take for your application? --- # Closed sprint - 👍 Shared control over workload - 👍 Predictible cadence - 👎 Limits response time to `sprint_length`

The story of a bug

10 May: 👷🏻‍♂️, 🤷‍♂️; 👷🏻‍♂️ →📧→ 🦹🏻‍♂️
11 May, 4 PM: 🦹🏻‍♂️ →📧→ 👷🏻‍♂️
15 May: 👷🏻‍♂️ →→ 👩🏾‍💻
16 May, 4 PM: 👩🏾‍💻 →→ 👷🏻‍♂️

# Pull Requests - Untrusted contributer send in patch - Trusted maintainer chooses what to merge - Communication through centralised repositor --- # Pull Requests - 👍 Multiple people look at the code - 👎 Time between action and response - 👎 Focus on code level, not product level - 👎 Value spends a lot of time waiting

The story of a bug

17 May: 👷🏻‍♂️ →→ 👩🏾‍💻
17 May, 3 PM: 👩🏾‍💻 →→ 👷🏻‍♂️
18 May: 👷🏻‍♂️ → 🕺⛺️🍻

The story of a bug

22 May: 🧑‍💼​ 🦸🏼‍♂️ 👩🏾‍💻 👷🏻‍♂️
30 May: 👷🏻‍♂️ →→ 👩🏾‍💻
30 May: 👩🏾‍💻 →✅→ 👷🏻‍♂️
2 June: 👩🏾‍💻 👷🏻‍♂️ →📦→ 👩🏼‍🚒

# Handoffs - Teams with distinct responsibilities - Changes move in discrete steps --- # Handoffs - 👍 Specialisation - 👍 Clear responsibilities - 👎 Pipeline speed - 👎 Adversarial relationships

The story of a bug

6 June, 7 AM: 👩🏼‍🚒 →📦→ ☁️
6 June, 9 AM: 🧑‍💼 →📧📧📧→ 🦹🏻‍♂️🦹🏻‍♂️🦹🏻‍♂️

# Time to value - The bug is fixed, 🦹🏻‍♂️ Customer can send their invoices again! - Took 5 weeks

Processes are there for a reason!

  • Quality assurance
  • Pace
  • Delivering software reliably

The story of a bug

6 June
🦹🏻‍♂️🤬 →📞→ 🧑‍💼
🧑‍💼😱 🦸🏼‍♂️ 👩🏾‍💻 👷🏻‍♂️
👩🏾‍💻 →🩹→ 👩🏼‍🚒
👩🏼‍🚒 →🩹→ ☁️

# What just happened? - High stress: angry phone calls - Value discovery, implementation, delivery
# Value stream mapping - How the *value* flows through an organisation - *Who* holds responsibility - Time to value

Continuous delivery

* Build quality in * Work in small batches * Computers perform repetitive tasks, people solve problems * Relentlessly pursue continuous improvement * Everyone is responsible

The deployment pipeline

...!!!
## Build quality in - Test Driven Development - Pair programming - Infrastructure as code
## Work in small batches - Continuous integration/Trunk based development - Feature flags - More frequent releases
## Computers perform repetitive tasks, people solve problems - Continuous deployment - Tacit knowledge → Text runbook → Script → Deployment pipeline
## Relentlessly pursue improvement - Do one step at a time - Find out (measure!) what works - "Make the change easy, then make the easy change"
## Everyone is responsible -
# What to do this Monday? * Sketch the value stream for a 1-hour - Discovery - Selection/prioritisation - Implementation - Verification - Delivery --- # What to do this Monday? * Build quality in - test-drive a larger user story - pair program for an hour daily - codify a text runbook --- # What to do this Monday? * Work in small batches - build a story on `main` behind a feature flag --- # What to do this Monday? * Computers perform repetitive tasks, people solve people-solve-problems - improve the automation of one repeating task --- # What to do this Monday? * Relentlessly pursue continuous improvement - got TDD? Go TCR: `(test && commit) || revert` - got a deploy script? Bring it to the deployment pipeline - got automated builds? Release each working build to acceptance - Refactor before implementation --- # What to do this Monday? * Everyone is responsible - have lunch with the 🦸🏼‍♂️ Ops team - need review? Sync with 👩🏾‍💻 Sr. Dev at your desk - need to review? Pair with 👷🏻‍♂️ Jr. Dev - propose process improvements --- # What to do this Monday? Ask *"Why can't we deploy this today?"* and automate the answer