How often do you release your product to your end users? How often do your end users see and use your product? Why is Continuous Delivery helping us to focus on business value? How can Scrum help us to be innovative? These and more questions are going to be answered in this talk about Scrum with Continuous Delivery. Companies and organizations struggle with bureaucracy, dependencies, silo thinking, human behavior and technical problems and loose the real goal. Continuous Delivery being more than a technical practice can work with Scrum and changes the way we write software completely. Let’s see how we can combine those and delight our customers with a constant flow of features and happiness. Target audience: Experienced Scrum Practitioners that would like to take the next step to delight their customers

1. Use
Scrum
and
Continuous Delivery
to
innovate like crazy
Peter Gfader
twitter.com/peitor

2. Your customer?
Image source: http://gifsoup.com/

3. Your customer?
Image source: http://pandawhale.com/post/10508/

4. ** Engage button **

5. About you

6. Scrum?

7. Scrum But?

8. Scrum And?

9. 1 LOC change
In Production?

10. Idea
In Production?

11. About me

12. Peter Gfader
peter.gfader@zuehlke.ch
http://blog.gfader.com
twitter.com/peitor

13. Image source: http://www.slideshare.net/jchyip

14. Insanity
Doing the same thing
over and over again
and expecting different results
Albert Einstein

17. Stresslevel
Release t

18. Deploy and Stress Test
every night

27. Our highest priority is to satisfy the customer
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software
1st principle of the Agile Manifesto

28. Our highest priority is to satisfy the customer
through early and continuous delivery
through early and continuous delivery
of valuable software
of valuable software
1st principle of the Agile Manifesto

29. Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software
1st principle of the Agile Manifesto

30. Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software
1st principle of the Agile Manifesto

31. How to delight our customers?
Image source: http://fourgifs.com

32. How to delight our customers?
Know their expectations

33. How to delight our customers?
Know their expectations
Talk to them
Image source: http://regretbeingaproductmanager.tumblr.com/post/45877228482

34. Set the stage

35. Scrum

37. Pain

38. PO knows our users?
Image source: http://www.flickr.com/photos/jurvetson/5314774452/

39. 4 Week Sprints

4 Week next Release
Image source: http://www.flickr.com/photos/biggreymare/3281787278

40. “Only Joe knows how to
deploy”

41. RTFM!?

42. From: SysAdmin
To: Peter Gfader
Please close the application
We deploy a new version
Restart your machine after lunch

43. Hard!
Image source: http://mrowkodzik.wordpress.com/2011/11/11/superbohaterowie/

44. Not fun!
Image source: http://gartner.com

45. Feature visible
> 2 years?
Image source: http://utahrepro.wordpress.com/2011/02/11/thats-a-waste-of-my-time/

46. Feature visible
> 2 years?
No one wants it?

47. Feature visible
> 2 years?
No one wants it?
Very expensive!

48. What is not
Continuous Delivery

49. !Continuous Delivery
“Production Hardware is ready in
1 year”

50. !Continuous Delivery
“Next 2 weeks we merge all
branches to main”

51. !Continuous Delivery
“Bugfix Sprint”

52. Continuous Delivery

53. Always Production Ready

54. No effort
automated
deployments
Image source: http://forgifs.com/

55. 1 Click Deployment

56. Continuous Delivery
“On Demand Delivery”

57. Deployment Pipeline

58. Why CD?

59. Less risk

60. Test the whole before go live

61. Easier
Image source: http://regretbeingaproductmanager.tumblr.com/post/44216498885/

62. Faster
Image source: http://vocaloid-review.tumblr.com/post/9141481879

63. Its cheaper to build
something in 2 weeks
…that no one wants

65. How CD?

66. 1/2 Everyone

67. 2/2 Automation

68. Scrum + CD
How?

69. 1/2
+ Done criteria
“Deployed to Test”

70. 2/2
+ Done criteria
“Deployed to Production”

75. Move single PBIs
from Idea
until Production

76. Move single PBIs
from Idea
until Production
“Swarming”

77. Clarification

78. Deployed
VS
Released

79. Deployed = Team
Released = Business

80. Feature Toggling

82. FTDD
as in
Feature Toggle
Driven Development
Paulo Caroli
http://agiletips.blogspot.ch/2013/02/toggle-driven-development.html

83. Release
• Event
• Location
• License
• Internal
• Written Manual ready

84. “2 concerns Peter!”

85. #1
“Works only for the web”

86. Screenshot from 2 Juli 2012

89. #2
“The cost is not worth doing this”

90. #1
Inventory = waste
Not released software is inventory
http://www.joelonsoftware.com/items/2012/07/09.html

91. #2
Bugs happen!
How long to release a bugfix?

92. #2
Bugs happen!
How long to release a bugfix?
Inclusive Tests for Regression +
Performance and Deployment?

93. What happens?

94. Short feedback cycles
Image source: http://www.flickr.com/photos/daninofal/6754602743/sizes/z/in/photostream/

95. Short feedback cycles
Nothing new!!!

96. The ”Waterfall model”
Royce, Winston (1970)
http://en.wikipedia.org/wiki/Waterfall_model

97. Seite 2

98. Seite 2

99. Feedback cycles

101. Increased collaboration

102. Test ideas in the market
#1/2

104. This feature is in Alpha stage

105. Sorry
We are not ready yet

106. Test ideas in the market
#2/2

111. Validated Learning

112. Image source: http://www.userdrivendev.com/p/build-measure-learn-loop_13.html

113. Innovation isn’t magic

114. Need for innovation?

115. Source: http://www.businessinsider.com/chart-of-the-day-apple-the-iphone-company-2012-1

116. Imagine

122. Deliver faster

123. Test ideas

124. Learn faster

125. Innovate

126. Build the right thing

127. Happy user
Image source: http://herrmedic.tumblr.com/post/22066048382/

128. Happy business
Image source: http://tumblr.com

129. Happy people!
Image source: http://gifsoup.com

130. Thanks!
peter.gfader@zuehlke.ch
http://blog.gfader.com
twitter.com/peitor

131. More?
Whitepaper
Use Scrum + Continuous Delivery
to build the right thing
http://www.scrum.org/Community/Community-Publications

132. More?

133. More?

134. http:// releasecadencereport.com
http://svy.mk/11xoY9A

135. ?

136. ** Rate **

137. Continue the conversation
peter.gfader@zuehlke.ch
twitter.com/peitor
http://blog.gfader.com