The Path to Continuous Delivery

An introduction to Continuous Delivery(CD) and what I believe are the core pillars to achieve CD (TDD, BDD and pair programming).

Presented at:
* Hong Kong Code Conf 2015
* Agile Tour Hong Kong 2016

Transcript

2. The Path to Continuous Delivery
3. Pedro Pimentel ”zukunftsalick” 
 in most social apps
4. Continuous Delivery to the Pub
5. 1 I'll send an email to everyone asking who wants to go to the pub after work.
6. 1 I'll send an email to everyone asking who wants to go to the pub after work. 2 I’m in.
7. 1 I'll send an email to everyone asking who wants to go to the pub after work. 5 6 4 3 2 I’m in.
8. 1 I'll send an email to everyone asking who wants to go to the pub after work. 5 6 4 3 2 I’m in. 7 I just need to finish a few things off. Can you wait 5 minutes?
9. 1 I'll send an email to everyone asking who wants to go to the pub after work. 5 6 4 3 2 I’m in. 7 I just need to finish a few things off. Can you wait 5 minutes? 8 I'll see you there, I'm gonna be here another half an hour at least.
10. 5 minutes later
12. 7 Sorry! I'll just be a couple more minutes late. 1 4 3 5 2 6
13. 7 Sorry! I'll just be a couple more minutes late. 1 4 3 5 2 6 9 If you wait for me, I’ll come too.
14. 7 Sorry! I'll just be a couple more minutes late. 1 4 3 5 2 6 9 If you wait for me, I’ll come too. 8 I’m nearly done! Wait for me!!!
15. By this time...
16. By this time... Half an hour has passed since #1 to #6 were ready to go.
17. By this time... Half an hour has passed since #1 to #6 were ready to go. #7 has already finished his work and joined the others.
18. By this time... Half an hour has passed since #1 to #6 were ready to go. #7 has already finished his work and joined the others. All of them are around #9 desk, waiting for him.
19. By this time... Half an hour has passed since #1 to #6 were ready to go. #7 has already finished his work and joined the others. All of them are around #9 desk, waiting for him. #8 joins the waiting crowd a few minutes later.
20. A few more minutes later
21. 9 I’m done! Let’s go!
22. 9 I’m done! Let’s go! 5 Oh Sh**! I forgot to send an email.
24. #4 goes to the toilet
25. #4 goes to the toilet In the meantime #5 comes back.
26. #4 goes to the toilet In the meantime #5 comes back. #1 is already regretting sending out the invitation.
27. One hour and fifteen minutes later.
28. 1 4 3 5 2 6 Lift 7 8 9
29. 1 4 3 5 2 6 7 8 9 Only one! We need three cabs! Let’s wait!
30. 1 4 3 5 2 6 7 8 9
31. #3 now has to go home to feed his cat.
32. It’s already 9:30pm, all other venues are packed so everyone else also goes home, unhappy and thirsty. #3 now has to go home to feed his cat.
33. Does it Sound Familiar?
34. 1 I'm off to the pub in 5 minutes sharp. There's some spaces in the cab. Anyone wanna join me?
35. 1 I'm off to the pub in 5 minutes sharp. There's some spaces in the cab. Anyone wanna join me? 4 3 2 I’m in.
36. 1 I'm off to the pub in 5 minutes sharp. There's some spaces in the cab. Anyone wanna join me? 4 3 2 I’m in. 5 6 Who’s next?
37. 1 I'm off to the pub in 5 minutes sharp. There's some spaces in the cab. Anyone wanna join me? 4 3 2 I’m in. 7 I just need to finish a few things off. Can you wait 5 minutes? 5 6 Who’s next?
38. 1 I'm off to the pub in 5 minutes sharp. There's some spaces in the cab. Anyone wanna join me? 4 3 2 I’m in. 7 I just need to finish a few things off. Can you wait 5 minutes? 8 I'll see you there, I'm gonna be here another half an hour at least. 5 6 Who’s next?
39. 1 4 3 2 It’s ok. Let’s move to the next one.
40. In the mean time...
41. #5 and #6 decided to wait for #7 to share a taxi. In the mean time...
42. #5 and #6 decided to wait for #7 to share a taxi. #8 says the same thing “oh, wait for me, I’m nearly done” In the mean time...
43. #5 and #6 decided to wait for #7 to share a taxi. #8 says the same thing “oh, wait for me, I’m nearly done” #9 says “I’m almost done too, you three go first and I split a taxi with #8” In the mean time...
44. At the pub 1 4 3 2
45. At the pub 1 4 3 2 5 6 7 #8 and #9 are coming, we should make space for them
46. Continuous Delivery!!!
47. Applying to software delivery
48. Can you think of examples? Are you one of the thirsty workers that could go to the pub but is still waiting for everyone?
49. Can you think of examples? Do you have working pieces of code, ready for deploy, that are waiting for colleagues? Are you one of the thirsty workers that could go to the pub but is still waiting for everyone?
50. Can you think of examples? Is the group of thirsty workers so big that whenever the chosen pub is closed, finding another pub in the busiest time is a difficult task?
51. Can you think of examples? Are the changes you deploy so big, that when something unexpected happens, you have to re-sync and deploy everything again? Is the group of thirsty workers so big that whenever the chosen pub is closed, finding another pub in the busiest time is a difficult task?
52. Can you think of examples? Do the pubs close or are packed before thirsty workers finally organize themselves and get out of the office?
53. Can you think of examples? Do you loose your opportunity window getting all teams in sync for a release? Do the pubs close or are packed before thirsty workers finally organize themselves and get out of the office?
54. Suggestions Find a pub that’s not far from the office. Have an agreement that every evening, if someone is thirsty, they just head to the pub, rather than organizing an outing.
55. Suggestions Find a pub that’s not far from the office. Have an agreement that every evening, if someone is thirsty, they just head to the pub, rather than organizing an outing. Working at the pub?
56. 1/2
57. Software Craftsmanship
58. Not only working software
    but also well-crafted software
    Not only responding to change
    but also steadily adding value
    Not only individuals and interactions
    but a community of professionals
    Not only customer collaboration
    but also productive partnerships
59. Well-crafted software.
60. Steadily adding value == Continuous Delivery
61. Give Back to the world
 == 
 Community of Professionals
62. Productive Partnership (aka the extra mile)
63. Core practices
64. BDD Behaviour Driven Development
66. “I want to save 40% on operational costs”
67. It has to be a description of a requirement and its business benefit, and a set of criteria by which we all agree that it is “done” Dan North
69. Story: Account Holder withdraws cash
70. Story: Account Holder withdraws cash As an Account Holder I want to withdraw cash from an ATM So that I can get money when the bank is closed
71. Story: Account Holder withdraws cash As an Account Holder I want to withdraw cash from an ATM So that I can get money when the bank is closed Scenario 1: Account has sufficient funds Given the account balance is $100 And the card is valid And the machine contains enough money When the Account Holder requests $20 Then the ATM should dispense $20 And the account balance should be $80 And the card should be returned
72. TDD Test Driven Development
73. TDD practices Define the API you want to use Write code based on facts Write just enough code to make test pass Read the tests to learn about someone’s else code
74. TDD practices Assert First One Assertion per test Faking/Stubbing/Mocking Triangulation
75. Red Green Refactor
76. Influence Diagrams
77. Pair Programming
78. eXtreme Programming Giles Bowkett blog
79. Sometimes in trio
80. Or in groups
81. Pair Rotation
82. Why? Economics Design Quality Satisfaction Learning Team building / Communication
83. Recapping BDD TDD Pair Programming Software Craftsmanship Steadily Adding Value
85. Thank you