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.
The Frontiers of
Continuous Delivery
Eberhard Wolff
@ewolff
http://ewolff.com
Fellow
http://continuous-delivery-buch.de/ http://continuous-delivery-book.com/
http://microservices-buch.de/ http://microservices-book.com/
http://microservices-book.com/
primer.html
http://microservices-buch.de/
ueberblick.html
FREE!!!!
Continuous Delivery –
Why Do I Even Care?
Faster Feedback
Implementation
Production Deployment
Lower Risk
> Much less deployed
> Less risk of a bug
> Easier to fall back
> …or add other
safeguards
Quarterly
Release
Da...
Higher Reliability
> Automated deployment and tests
> …easy to reproduce
> ...faster
> ...executed frequently
Commit
Stage...
Principles Agile Manifesto
Our highest priority is
to satisfy the customer
through early and
continuous delivery
of valuab...
Continuous Delivery:
Why Do I Even Care?
> Faster Feedback
> Lower Risk
> Higher Reliability
> Value to the customer
> I’m...
2010: Continuous
Delivery is the next
big thing!
Continuous Delivery
will increase
productivity!
Continuous Delivery
should obviously be
the way to go.
Continuous Delivery =
Technical Issue
Continuous Delivery =
Technical Issue
Deployment
No
2017: Lots of tools to
solve technical
issues.
Continuous Delivery is
People.
Frontier:
Business
Faster Feedback
Implementation
Production Deployment
Business
Metrics
Business
Features
How Business Works
> Release Q1/2018
> Here are the features!
> Go!
60%– 90% of ideas
do not improve the
metrics they were
intended to improve
Ronny Kohavi
Former Head Data Mining and Person...
Just Waste
> More than half of the
features are
worthless…
> ...or hurt business
goals.
> Many businesses
doesn’t even kno...
Run a minimal feature
by users.
Implementation
Production Deployment
Business
Metrics
Business
Features
Related to MVP (Mi...
Survival is
Optional.
> Fast releases lead to
better software and
products.
> Bad products die out.
> Continuous delivery:
The only way to
succe...
IT
Chauvinism
Ways to Compete
> More features faster
> …or...
> Trust
> Existing customer relations
> Would your grandpa choose
a FinTec...
Continuous Delivery: No
> Diesel update at VW and
Audi
> 4.000.000 cars going to
the garage just for a
software update.
> ...
Continuous Delivery: Yes
> Tesla
> New features like
> …more speed
> …more range during hurricane Irma
> …self-driving
> ....
http://spon.de/ae3nr
Even for cars
most features are
software now.
Even for cars
you can do
continuous delivery.
So you really don’t see any
value?
You really can’t do
Continuous Delivery?
Business
> …could get the biggest benefit
> ...but often doesn‘t
> Product development in small batches is
different from ...
Extending
the frontier
Is Continuous Delivery
worth it without business
support?
YES!!
> Faster Feedback
> Lower Risk
> Higher Reliability
> Value to the customer
Extending the
Business Frontier
> Ambitious: IT drives the business
> Not too much influence?
> IT sometimes only think th...
Frontier:
People
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev OpsCustomer
QA & CD
> Quality Assurance (QA) must
provide tests
> …or at least support testing
> Automated tests
> Manual tests too sl...
QA & CD
> Traditional Quality Assurance (QA)
focuses on manual tests.
> Mind shift
> …and different skills
QA
Customer
> Customer must provide
information for automated
acceptance test
> No more manual sign-off
> Needs trust
> …and ...
Ops
> One month waiting for a database
> …that is cheaply provided by a
highly optimized Ops team
> …for “cost”
> Ops has ...
Dev
> Can automate
> i.e. develop software
> …but have limited knowledge
about the other topics.
Dev
Software = Automation
Software = Automation
Still automating CD is hard!
Extending
the frontier
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev OpsCustomer
Educate & Collaborate
> Dev do automation all
day.
> Make all aware of the
needed collaboration
> Encourage collaboration
...
Ops Dev
Why the heck all
the servers?
What do you
even know about
architecture?
Is reorganization really the solution?
Ops
Dev
Let’s reduce
Critical bugs in
production!
QA
Reduced critical
bugs by >50%.
Collaboration
despite
org separation
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
Dev
Dev DevDev
Dev
> Dev takes over the other roles.
> Happening in practice
> …but not a strategy
> Unused QA / Ops skills Dev
2012: Talk about
Linux namespaces,
AuFS and cgroups at a
developer
conference?
2017: Docker at every
developer conference
Dev is learning Ops
skills.
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev OpsCustomer
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev Customer
PaaS
> Cloud Foundry, Openshift,
Kubernetes
> Install a PaaS once
(challenge)
> All future deployments via PaaS
> Technolo...
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev OpsCustomer
Commit
Stage
Automated
Acceptance
Testing
Automated
Capacity
Testing
Manual
Explorative
Testing
Release
QA
Dev Customer
Public Cloud
> Two minutes for a
database instead of one
month
> Many predefined
offerings for Big Data,
messaging…
> ...b...
Cross-functional Team
> Was: teams with broad
skill set
> i.e. frontend, backend,
database
> Benefits agility:
Can work on...
More Cross-functional Team
> Include QA, Ops
> …even business
> Might build guilds to
foster knowledge
exchange
> Spotify
...
More Cross-functional Team
> Can be led by business
goals
> Can enable self
organization
> Huge organizational shift
> Wha...
Frontier:
Management Buy-in
Just like Agility
Agility in the Nineties
> Grassroots movement
> The future of development!
> Teams want to do it.
> Management: Na, how ca...
Agility Now
> Management: We do Scrum
> Teams skeptical or uninterested
> Business finds it hard to reap the benefits
> St...
Agility Now
> Need more than lip service
> …convincing
> http://blog.johanneslink.net/
2011/12/02/say-goodbye-i-wont-be-ba...
Extending
the frontier
CD & Management Buy-In
> Management buy-in won‘t solve the
problems!
> It just means there will be other problems.
> Still...
Conclusion
Conclusion
> Technological problems mostly solved
> Microservices might support Continuous
Delivery.
Continuous Delivery is
People.
Gerald Weinberg‘s
2nd Law of Consulting:
No matter how it looks at
first,
it's always a people
problem.
EMail bedcon2017@ewolff.com to get:
Slides
+ Microservices Primer
+ Sample Microservices Book
+ Sample of Continuous Deliv...
The Frontiers of Continuous Delivery
The Frontiers of Continuous Delivery
The Frontiers of Continuous Delivery
Upcoming SlideShare
Loading in …5
×

The Frontiers of Continuous Delivery

420 views

Published on

Continuous Delivery solves many current challenges - but still adoption is limited. This talks shows reasons for this and how to overcome these problems.

Published in: Software
  • Be the first to comment

The Frontiers of Continuous Delivery

  1. 1. The Frontiers of Continuous Delivery Eberhard Wolff @ewolff http://ewolff.com Fellow
  2. 2. http://continuous-delivery-buch.de/ http://continuous-delivery-book.com/
  3. 3. http://microservices-buch.de/ http://microservices-book.com/
  4. 4. http://microservices-book.com/ primer.html http://microservices-buch.de/ ueberblick.html FREE!!!!
  5. 5. Continuous Delivery – Why Do I Even Care?
  6. 6. Faster Feedback Implementation Production Deployment
  7. 7. Lower Risk > Much less deployed > Less risk of a bug > Easier to fall back > …or add other safeguards Quarterly Release Daily Release
  8. 8. Higher Reliability > Automated deployment and tests > …easy to reproduce > ...faster > ...executed frequently Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release
  9. 9. Principles Agile Manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  10. 10. Continuous Delivery: Why Do I Even Care? > Faster Feedback > Lower Risk > Higher Reliability > Value to the customer > I’m in!
  11. 11. 2010: Continuous Delivery is the next big thing!
  12. 12. Continuous Delivery will increase productivity!
  13. 13. Continuous Delivery should obviously be the way to go.
  14. 14. Continuous Delivery = Technical Issue
  15. 15. Continuous Delivery = Technical Issue Deployment
  16. 16. No
  17. 17. 2017: Lots of tools to solve technical issues.
  18. 18. Continuous Delivery is People.
  19. 19. Frontier: Business
  20. 20. Faster Feedback Implementation Production Deployment Business Metrics Business Features
  21. 21. How Business Works > Release Q1/2018 > Here are the features! > Go!
  22. 22. 60%– 90% of ideas do not improve the metrics they were intended to improve Ronny Kohavi Former Head Data Mining and Personalization group Amazon Source: Lean Enterprise, Humble et al
  23. 23. Just Waste > More than half of the features are worthless… > ...or hurt business goals. > Many businesses doesn’t even know the KPIs.
  24. 24. Run a minimal feature by users. Implementation Production Deployment Business Metrics Business Features Related to MVP (Minimal Viable Product)
  25. 25. Survival is Optional.
  26. 26. > Fast releases lead to better software and products. > Bad products die out. > Continuous delivery: The only way to succeed for a business.
  27. 27. IT Chauvinism
  28. 28. Ways to Compete > More features faster > …or... > Trust > Existing customer relations > Would your grandpa choose a FinTech over a bank?
  29. 29. Continuous Delivery: No > Diesel update at VW and Audi > 4.000.000 cars going to the garage just for a software update. > How much does that cost? > Per car 70€ > Total 280.000.000€https://heise.de/newsticker/meldung/Volkswagen-Haendler-Software-Update-taugt-nicht-3834343.html http://www.handelsblatt.com/my/unternehmen/industrie/volkswagen-vier-millionen-diesel-autos-erhalten-update/20139344.html
  30. 30. Continuous Delivery: Yes > Tesla > New features like > …more speed > …more range during hurricane Irma > …self-driving > ...summoning > etc..
  31. 31. http://spon.de/ae3nr
  32. 32. Even for cars most features are software now.
  33. 33. Even for cars you can do continuous delivery.
  34. 34. So you really don’t see any value? You really can’t do Continuous Delivery?
  35. 35. Business > …could get the biggest benefit > ...but often doesn‘t > Product development in small batches is different from the known ways… > ...and some businesses are not under a lot of pressure.
  36. 36. Extending the frontier
  37. 37. Is Continuous Delivery worth it without business support?
  38. 38. YES!!
  39. 39. > Faster Feedback > Lower Risk > Higher Reliability > Value to the customer
  40. 40. Extending the Business Frontier > Ambitious: IT drives the business > Not too much influence? > IT sometimes only think they know better > Educate business > …or focus on other values
  41. 41. Frontier: People
  42. 42. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev OpsCustomer
  43. 43. QA & CD > Quality Assurance (QA) must provide tests > …or at least support testing > Automated tests > Manual tests too slow > …and too error prone QA
  44. 44. QA & CD > Traditional Quality Assurance (QA) focuses on manual tests. > Mind shift > …and different skills QA
  45. 45. Customer > Customer must provide information for automated acceptance test > No more manual sign-off > Needs trust > …and trust! > ...and some technical literacy Customer
  46. 46. Ops > One month waiting for a database > …that is cheaply provided by a highly optimized Ops team > …for “cost” > Ops has very different incentives > …and doesn‘t even work in projects. Ops
  47. 47. Dev > Can automate > i.e. develop software > …but have limited knowledge about the other topics. Dev
  48. 48. Software = Automation
  49. 49. Software = Automation Still automating CD is hard!
  50. 50. Extending the frontier
  51. 51. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev OpsCustomer
  52. 52. Educate & Collaborate > Dev do automation all day. > Make all aware of the needed collaboration > Encourage collaboration > Not necessarily an org chart change
  53. 53. Ops Dev Why the heck all the servers? What do you even know about architecture? Is reorganization really the solution?
  54. 54. Ops Dev Let’s reduce Critical bugs in production! QA Reduced critical bugs by >50%. Collaboration despite org separation
  55. 55. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Dev Dev DevDev
  56. 56. Dev > Dev takes over the other roles. > Happening in practice > …but not a strategy > Unused QA / Ops skills Dev
  57. 57. 2012: Talk about Linux namespaces, AuFS and cgroups at a developer conference?
  58. 58. 2017: Docker at every developer conference
  59. 59. Dev is learning Ops skills.
  60. 60. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev OpsCustomer
  61. 61. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev Customer
  62. 62. PaaS > Cloud Foundry, Openshift, Kubernetes > Install a PaaS once (challenge) > All future deployments via PaaS > Technology to solve the social DevOps issue > …but is there any disadvantage?
  63. 63. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev OpsCustomer
  64. 64. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev Customer
  65. 65. Public Cloud > Two minutes for a database instead of one month > Many predefined offerings for Big Data, messaging… > ...but off premise > A problem or a strategy to keep your job?
  66. 66. Cross-functional Team > Was: teams with broad skill set > i.e. frontend, backend, database > Benefits agility: Can work on meaningful business features Frontend Backend Database
  67. 67. More Cross-functional Team > Include QA, Ops > …even business > Might build guilds to foster knowledge exchange > Spotify Dev QA Ops Business
  68. 68. More Cross-functional Team > Can be led by business goals > Can enable self organization > Huge organizational shift > What happened to managers??? > Management buy-in? Dev QA Ops Business
  69. 69. Frontier: Management Buy-in
  70. 70. Just like Agility
  71. 71. Agility in the Nineties > Grassroots movement > The future of development! > Teams want to do it. > Management: Na, how can you delivery software without a huge sophisticated plan?
  72. 72. Agility Now > Management: We do Scrum > Teams skeptical or uninterested > Business finds it hard to reap the benefits > Still traditional product development.
  73. 73. Agility Now > Need more than lip service > …convincing > http://blog.johanneslink.net/ 2011/12/02/say-goodbye-i-wont-be-back/
  74. 74. Extending the frontier
  75. 75. CD & Management Buy-In > Management buy-in won‘t solve the problems! > It just means there will be other problems. > Still: try to convince management.
  76. 76. Conclusion
  77. 77. Conclusion > Technological problems mostly solved > Microservices might support Continuous Delivery.
  78. 78. Continuous Delivery is People.
  79. 79. Gerald Weinberg‘s 2nd Law of Consulting: No matter how it looks at first, it's always a people problem.
  80. 80. EMail bedcon2017@ewolff.com to get: Slides + Microservices Primer + Sample Microservices Book + Sample of Continuous Delivery Book Powered by Amazon Lambda & Microservices

×