Use Scrum and Continuous Delivery to innovate like crazy!

2,521 views

Published on

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

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,521
On SlideShare
0
From Embeds
0
Number of Embeds
58
Actions
Shares
0
Downloads
28
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Use Scrum and Continuous Delivery to innovate like crazy!

  1. 1. Use Scrum andContinuous Delivery toinnovate like crazy Peter Gfader twitter.com/peitor
  2. 2. Your customer?Image source: http://gifsoup.com/
  3. 3. Your customer?Image source: http://pandawhale.com/post/10508/
  4. 4. ** Engage button **
  5. 5. About you
  6. 6. Scrum?
  7. 7. Scrum But?
  8. 8. Scrum And?
  9. 9. 1 LOC changeIn Production?
  10. 10. IdeaIn Production?
  11. 11. About me
  12. 12. Peter Gfaderpeter.gfader@zuehlke.chhttp://blog.gfader.comtwitter.com/peitor
  13. 13. Image source: http://www.slideshare.net/jchyip
  14. 14. Insanity Doing the same thing over and over againand expecting different results Albert Einstein
  15. 15. Stresslevel Release t
  16. 16. Deploy and Stress Test every night
  17. 17. Our highest priority is to satisfy the customerOur highest priority is to satisfy the customer through early and continuous delivery of valuable software 1st principle of the Agile Manifesto
  18. 18. 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
  19. 19. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software 1st principle of the Agile Manifesto
  20. 20. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software 1st principle of the Agile Manifesto
  21. 21. How to delight our customers?Image source: http://fourgifs.com
  22. 22. How to delight our customers? Know their expectations
  23. 23. How to delight our customers? Know their expectations Talk to themImage source: http://regretbeingaproductmanager.tumblr.com/post/45877228482
  24. 24. Set the stage
  25. 25. Scrum
  26. 26. Pain
  27. 27. PO knows our users?Image source: http://www.flickr.com/photos/jurvetson/5314774452/
  28. 28. 4 Week Sprints  4 Week next ReleaseImage source: http://www.flickr.com/photos/biggreymare/3281787278
  29. 29. “Only Joe knows how to deploy”
  30. 30. RTFM!?
  31. 31. From: SysAdminTo: Peter GfaderPlease close the applicationWe deploy a new versionRestart your machine after lunch
  32. 32. Hard!Image source: http://mrowkodzik.wordpress.com/2011/11/11/superbohaterowie/
  33. 33. Not fun!Image source: http://gartner.com
  34. 34. Feature visible > 2 years?Image source: http://utahrepro.wordpress.com/2011/02/11/thats-a-waste-of-my-time/
  35. 35. Feature visible > 2 years?No one wants it?
  36. 36. Feature visible > 2 years?No one wants it?Very expensive!
  37. 37. What is notContinuous Delivery
  38. 38. !Continuous Delivery“Production Hardware is ready in 1 year”
  39. 39. !Continuous Delivery“Next 2 weeks we merge all branches to main”
  40. 40. !Continuous Delivery “Bugfix Sprint”
  41. 41. Continuous Delivery
  42. 42. Always Production Ready
  43. 43. No effort automated deploymentsImage source: http://forgifs.com/
  44. 44. 1 Click Deployment
  45. 45. Continuous Delivery“On Demand Delivery”
  46. 46. Deployment Pipeline
  47. 47. Why CD?
  48. 48. Less risk
  49. 49. Test the whole before go live
  50. 50. EasierImage source: http://regretbeingaproductmanager.tumblr.com/post/44216498885/
  51. 51. FasterImage source: http://vocaloid-review.tumblr.com/post/9141481879
  52. 52. Its cheaper to buildsomething in 2 weeks …that no one wants
  53. 53. How CD?
  54. 54. 1/2 Everyone
  55. 55. 2/2 Automation
  56. 56. Scrum + CD How?
  57. 57. 1/2 + Done criteria“Deployed to Test”
  58. 58. 2/2 + Done criteria“Deployed to Production”
  59. 59. Move single PBIs from Ideauntil Production
  60. 60. Move single PBIs from Ideauntil Production “Swarming”
  61. 61. Clarification
  62. 62. Deployed VSReleased
  63. 63. Deployed = TeamReleased = Business
  64. 64. Feature Toggling
  65. 65. FTDD as in Feature Toggle Driven Development Paulo Carolihttp://agiletips.blogspot.ch/2013/02/toggle-driven-development.html
  66. 66. Release• Event• Location• License• Internal• Written Manual ready
  67. 67. “2 concerns Peter!”
  68. 68. #1“Works only for the web”
  69. 69. Screenshot from 2 Juli 2012
  70. 70. #2“The cost is not worth doing this”
  71. 71. #1 Inventory = waste Not released software is inventoryhttp://www.joelonsoftware.com/items/2012/07/09.html
  72. 72. #2 Bugs happen!How long to release a bugfix?
  73. 73. #2 Bugs happen! How long to release a bugfix?Inclusive Tests for Regression +Performance and Deployment?
  74. 74. What happens?
  75. 75. Short feedback cyclesImage source: http://www.flickr.com/photos/daninofal/6754602743/sizes/z/in/photostream/
  76. 76. Short feedback cycles Nothing new!!!
  77. 77. The ”Waterfall model” Royce, Winston (1970)http://en.wikipedia.org/wiki/Waterfall_model
  78. 78. Seite 2
  79. 79. Seite 2
  80. 80. Feedback cycles
  81. 81. Increased collaboration
  82. 82. Test ideas in the market #1/2
  83. 83. This feature is in Alpha stage
  84. 84. SorryWe are not ready yet
  85. 85. Test ideas in the market #2/2
  86. 86. Validated Learning
  87. 87. Image source: http://www.userdrivendev.com/p/build-measure-learn-loop_13.html
  88. 88. Innovation isn’t magic
  89. 89. Need for innovation?
  90. 90. Source: http://www.businessinsider.com/chart-of-the-day-apple-the-iphone-company-2012-1
  91. 91. Imagine
  92. 92. Deliver faster
  93. 93. Test ideas
  94. 94. Learn faster
  95. 95. Innovate
  96. 96. Build the right thing
  97. 97. Happy userImage source: http://herrmedic.tumblr.com/post/22066048382/
  98. 98. Happy businessImage source: http://tumblr.com
  99. 99. Happy people!Image source: http://gifsoup.com
  100. 100. Thanks!peter.gfader@zuehlke.ch http://blog.gfader.com twitter.com/peitor
  101. 101. More?WhitepaperUse Scrum + Continuous Delivery to build the right thinghttp://www.scrum.org/Community/Community-Publications
  102. 102. More?
  103. 103. More?
  104. 104. http:// releasecadencereport.comhttp://svy.mk/11xoY9A
  105. 105. ?
  106. 106. ** Rate **
  107. 107. Continue the conversation peter.gfader@zuehlke.ch twitter.com/peitor http://blog.gfader.com

×