innovate like crazy
play

innovate like crazy Peter Gfader twitter.com/ peitor Your customer? - PowerPoint PPT Presentation

Use Scrum and Continuous Delivery to innovate like crazy Peter Gfader twitter.com/ peitor Your customer? Image source: http://gifsoup.com/ Your customer? Image source: http://pandawhale.com/post/10508/ ** Engage button ** About you


  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

  15. Stresslevel t Release

  16. Deploy and Stress Test every night

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

  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 1 st principle of the Agile Manifesto

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

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

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

  22. How to delight our customers? Know their expectations

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

  24. Set the stage

  25. Scrum

  26. Pain

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

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

  29. “Only Joe knows how to deploy”

  30. RTFM!?

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

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

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

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

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

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

  37. What is not Continuous Delivery

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

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

  40. ! Continuous Delivery “ Bugfix Sprint”

  41. Continuous Delivery

  42. Always Production Ready

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

  44. 1 Click Deployment

  45. Continuous Delivery “On Demand Delivery”

  46. Deployment Pipeline

  47. Why CD?

  48. Less risk

  49. Test the whole before go live

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

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

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

  53. How CD?

  54. 1/2 Everyone

  55. 2/2 Automation

  56. Scrum + CD How?

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

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

  59. Move single PBIs from Idea until Production

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

  61. Clarification

  62. Deployed VS Released

  63. Deployed = Team Released = Business

  64. Feature Toggling

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

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

  67. “2 concerns Peter!”

  68. #1 “Works only for the web”

  69. Screenshot from 2 Juli 2012

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

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

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

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

  74. What happens?

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

  76. Short feedback cycles Nothing new!!!

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

  78. Seite 2

  79. Seite 2

  80. Feedback cycles

Recommend


More recommend