# 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

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 boom. 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 * Control emotions

# Emotional regulation in software delivery 🏗️🏗️ * Apply brakes - Commit to an *acceptable* workload - Communicate about your needs

# 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

TOC