# 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
* 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
# What to do this Monday?
* 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?
Continuous delivery
* Build quality in
* Work in small batches
* Computers perform repetitive tasks, people solve problems
* Relentlessly pursue continuous improvement
* Everyone is responsible
