Fearless Software Delivery

Fear is the enemy of innovation and creative experimentation. Yet so many developers feel anxious when they’re about to release their feature to production. We’ll look at how to make your team fearless by increasing the chance of getting it right, and by reducing the cost for when you get it wrong.

Transcript

1. FEARLESS SOFTWARE DELIVERY @marcusolsson
2. FEARLESS SOFTWARE DELIVERY @marcusolsson
3. FEAR Anxiety PANIC! Nervousness @marcusolsson
5. PROBABILITY of SUCCESS
6. RELEASE OFTEN 1 UNTIL IT DOESN’T HURT ANYMORE @marcusolsson
7. RELEASE SMALLER 2 SMALLER CHANGES ARE EASIER TO UNDERSTAND @marcusolsson
8. AUTOMATE 3 TO REDUCE HUMAN ERROR @marcusolsson
9. WRITE TESTS 4 VERIFYING THE KNOWNS @marcusolsson
10. COST of FAILURE
11. impact = function(time, scope, severity) @marcusolsson
12. TIME 1 HOW LONG WAS THE BUG IN EFFECT? @marcusolsson
13. CATCH BUGS EARLY with MONITORING TIME 1 @marcusolsson
14. SCOPE 2 HOW MANY USERS WERE AFFECTED? @marcusolsson
15. LIMIT BLAST RADIUS with GRADUAL RELEASES SCOPE 2 @marcusolsson
16. SEVERITY 3 HOW BAD IS IT? @marcusolsson
17. FACE YOUR NIGHTMARES with CONTROLLED EXPERIMENTS SEVERITY 3 @marcusolsson
19. SOCIAL COST of FAILURE
20. YOU WILL FAIL
21. FAIL WITH CONFIDENCE @marcusolsson
22. FAIL WITH CONFIDENCE Increase the probability of success by releasing small, tested changes, often. Reduce the cost of failure through monitoring, gradual releases and controlled experiments @marcusolsson
23. FAIL WITH CONFIDENCE Reduce the social cost of failure with Curiosity and empathy instead of blaming @marcusolsson