Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Pat Hermens
Pepijn Sitter
What?
Faster to master, without disaster
Automated
deployments to
Production
Faster
Deployed in
minutes
Faster
One branch to
rule them all
Master
Code review
Without disaster
Automation
Without disaster
Monitoring
Without disaster
No disaster!
Surely, you have
some questions…
But I can't, because...
Scrum says:
‘potentially
releasable product
at the end of each
Sprint’
"Someone needs
to approve my
changes"
"We aren't allowed
to touch
Production"
"We have multiple
environments"
"Our applications
need to be
certified"
"Our application
landscape is really
complex"
"Change is hard"
Why?
No complex
planning is
necessary
Complicated
merges don’t exist
Remove all
"overhead"
Make “Elke dag
een beetje beter"
Empower your
teams
Deliver value as
fast as possible
How?
Circle of life
Developing
TestingDeploying
Monitoring
Very short-
lived branches
Developing
Feature
toggles
Developing
Automated
code analysis
Developing
Peer review
Developing
Developing
TestingDeploying
Monitoring
End-to-end
Integration
Module
Unit
End-to-end
Integration
Module
Unit
End-to-end
Integration
Module
Unit
End-to-end
Integration
Module
Unit
End-to-end
Integration
Module
Unit
End-to-end
Integration
Module
Unit
Developing
TestingDeploying
Monitoring
Automated
deployment
pipeline
Deploying
Straight to
Production
Deploying
Infrastructure
Deploying
Developing
TestingDeploying
Monitoring
Monitoring
Monitoring
Define key
metrics
Monitoring
Be the first to
know!
Monitoring
Failure is
always an
option...
Monitoring
…but it looks
like this
Monitoring
You make it;
you own it
Monitoring
Developing
TestingDeploying
Monitoring
There is no
master plan
YOU can do this
Questions?
Thanks!
© 2016 Microsoft Corporation. All rights reserved.
Faster to Master without Disaster
Faster to Master without Disaster
Faster to Master without Disaster
Faster to Master without Disaster
Faster to Master without Disaster
Faster to Master without Disaster
Faster to Master without Disaster
Upcoming SlideShare
Loading in …5
×

Faster to Master without Disaster

Is it really possible to have your code deployed to production in under in 10 minutes? The ultimate goal of every developer should be to deploy his/her code to production. The sooner your end users will be able to use your feature, the sooner the true business value of the feature kicks in. In this #Devops tale ‘Faster to master without disaster’ Pat Hermens and Pepijn Sitter will take you on a journey on how to achieve this without losing sanity. They each work in very different environments and offer you practical insights into the choices they made in order to help their teams succeed at delivering their software.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

  • Be the first to like this

Faster to Master without Disaster

  1. 1. Pat Hermens
  2. 2. Pepijn Sitter
  3. 3. What?
  4. 4. Faster to master, without disaster
  5. 5. Automated deployments to Production Faster
  6. 6. Deployed in minutes Faster
  7. 7. One branch to rule them all Master
  8. 8. Code review Without disaster
  9. 9. Automation Without disaster
  10. 10. Monitoring Without disaster
  11. 11. No disaster!
  12. 12. Surely, you have some questions…
  13. 13. But I can't, because...
  14. 14. Scrum says: ‘potentially releasable product at the end of each Sprint’
  15. 15. "Someone needs to approve my changes"
  16. 16. "We aren't allowed to touch Production"
  17. 17. "We have multiple environments"
  18. 18. "Our applications need to be certified"
  19. 19. "Our application landscape is really complex"
  20. 20. "Change is hard"
  21. 21. Why?
  22. 22. No complex planning is necessary
  23. 23. Complicated merges don’t exist
  24. 24. Remove all "overhead"
  25. 25. Make “Elke dag een beetje beter"
  26. 26. Empower your teams
  27. 27. Deliver value as fast as possible
  28. 28. How?
  29. 29. Circle of life
  30. 30. Developing TestingDeploying Monitoring
  31. 31. Very short- lived branches Developing
  32. 32. Feature toggles Developing
  33. 33. Automated code analysis Developing
  34. 34. Peer review Developing
  35. 35. Developing TestingDeploying Monitoring
  36. 36. End-to-end Integration Module Unit
  37. 37. End-to-end Integration Module Unit
  38. 38. End-to-end Integration Module Unit
  39. 39. End-to-end Integration Module Unit
  40. 40. End-to-end Integration Module Unit
  41. 41. End-to-end Integration Module Unit
  42. 42. Developing TestingDeploying Monitoring
  43. 43. Automated deployment pipeline Deploying
  44. 44. Straight to Production Deploying
  45. 45. Infrastructure Deploying
  46. 46. Developing TestingDeploying Monitoring
  47. 47. Monitoring
  48. 48. Monitoring
  49. 49. Define key metrics Monitoring
  50. 50. Be the first to know! Monitoring
  51. 51. Failure is always an option... Monitoring
  52. 52. …but it looks like this Monitoring
  53. 53. You make it; you own it Monitoring
  54. 54. Developing TestingDeploying Monitoring
  55. 55. There is no master plan
  56. 56. YOU can do this
  57. 57. Questions?
  58. 58. Thanks!
  59. 59. © 2016 Microsoft Corporation. All rights reserved.

×