Rational User Group - May 2014 Stockholm - DevOps from an EA perspective

100 %
0 %
Information about Rational User Group - May 2014 Stockholm - DevOps from an EA perspective

Published on May 8, 2014

Author: JoakimLindbom

Source: slideshare.net


How could DevOps help major corporations break out of the legacy problem? Why is rapid deployment needed to go for an agile delivery?

Rational User Group 2014-05-06 Joakim Lindbom Principal | Enterprise Architect

Today’s themes - Why do you need DevOps? - Squish’m bugs early! - Why do you need to deploy 10 times/day?

Now, what’s this?

Speed Kills!

Speed Kills!

0 10 20 30 40 50 60 70 80 90 100 2001 2003 2005 2007 2009 2011 2013 2015 Best & Beautiful A Inc B Inc C Inc Lack of speed kills!

The amount of caos increases by itself Termodynamics 2:a main law

DevOps is about increasing your responsiveness to customers

Devs  New features Ops  Uptime, uptime & uptime But – whatif Devs were meassured on uptime & Ops on new features? Just a thought….

Squish’m bugs early! Why? Because Early = Cheap

Reqs Specify system Build SW Design system Write code Build system Install system Test Reqs Test Specs Integr. test Test design Unit test System test UAT Design-Build-Run approach A bit too waterfallish

Reqs Specify system Build SW Design system Write code Build system Install system Test Reqs Test Specs Integr. test Test design Unit test System test UAT Design-Build-Run approach A bit too waterfallish

Cloud = access to abundance

Cloud = access to abundance You can have as many development, test & staging environments as you like! But you cannot handle this manually!


Zero-Day forever Your time to react on errors will approach ZERO Will become reality with the growing mobile market and IoT.

Big IT  Slow IT (not slow as in slow food….)

3% 2% 3% 3% 12% 10% 8% 8% 39% 33% 25% 22% 36% 42% 43% 46% 12% 15% 22% 23% CEO/ President/ Managing Director C-Level executives and board members Managers Staff Very Fast Fast About right Slow Very Slow How slow is slow?OFF THE PACE The pace of digital transformation is too slow – unless you’re the CEO. Who are these guys?!? MIT Center for Digital Business and Capgemini Consulting

IT Legacy is #1 obstacle for innovation Major corporations depend on core systems that - Are 15-20 years old - 3-4 persons know - Some staff is retired, some will be it within 4-5 years - Technology support is slow - Are somewhat documented - Have few formal test cases, but the staff know how to test Application Landscape Report 2014

IT Legacy is #1 obstacle for innovation Major corporations depend on core systems that - Are 25-45 years old - 1-2 persons know - All staff are retired, or will be it within 2-3 years - Technology support is gone - Are undocumented - Have no/few formal test cases Application Landscape Report 2014

The ability to innovate is strictly coupled with the ability to fail fast

Ten Observations on IT Complexity 1. Most IT systems are too complex. 2. "Best Practices" increase complexity. 3. Complex systems cost more to build. 4. Complex systems are harder to deliver. 5. Complex systems are less secure. 6. Complex systems are less reliable. 7. Complex systems are less agile. 8. Complex systems cost more to run. 10. Existing management approaches ignore complexity.

But what is SimpleIT? 1. Non complex 2. Small building blocks 3. Autonomous 4. They “know nothing” 5. Service based 6. Dynamic 7. Like lego bricks 8. Expose an OpenAPI 10. Connect development and operations

But what is SimpleIT? Simplified Modularised Optimised Hardened

Autonomous system? Totally separate parts Separate lifecycle! Loose coupling paw rihk-titt

System Stuff Data Autonomous system? We used to look at it from a technical boundaries perspective

System Stuff Data DevsArchitect Ops Autonomous system? But in order to unsure agilit, we need to include the people in the system definition

System Stuff Data DevsArchitect Ops OpenAPI Autonomous system? OpenAPI mindset = not a solution design for a specific purpose/project. Open for Innovation

~Autonomous system? Release = just a mountain to climb…

Basics, get things in order Ad-hoc deployment Structured & planned releases Major event Major RISKMajor hurdle

Climbing a Release-mountain, how many people experience it…

Industrialisation of IT IT development more and more viewed as "manufacturing" Square boxes, repeat over and over IT is innovationMistake!

How good is good? Compileable? No warnings? Runnable? Passing tests? Not breaking anything else? When your developers check in code, how good does it need to be?

Deploy 10 time per day How will that help you?

Deploy often Shorten feedback-loop Bring back passion – show visible result early Allow (small) failures Allow experimentation Follow Moore’s law Learn by doing But deploying often doesn’t mandate deploying to production equally often!

Deploy often Basis for Continuous Improvement Slow break-down into µServices Gradual transition towards smaller building blocks

Continous improvement Continuous rebuilding Always. Even if “not needed”

Summing up DevOps – increase responsiveness Lack of speed kills Simplify, make smaller & rebuild – to fight complexity Big kills!

Contact Joakim Lindbom Principal | Enterprise Architect Joakim.Lindbom@capgemini.com 08-5368 3934 0708-166404 twitter: JoakimLindbom http://www.slideshare.net/JoakimLindbom http://www.linkedin.com/in/joakimlindbom Insert contact picture

Image sources, marked as OK to use commercially https://upload.wikimedia.org/wikipedia/commons/8/8b/Buck_Mountain_Grand_Teton_NP1.jpg https://upload.wikimedia.org/wikipedia/commons/d/de/Eisklettern_kl_engstligenfall.jpg https://c1.staticflickr.com/1/1/1118807_a751d65ba5_z.jpg?zz=1 https://upload.wikimedia.org/wikipedia/commons/4/4f/Eternal_clock.jpg https://c1.staticflickr.com/9/8062/8189938256_2a683d2334_z.jpg https://upload.wikimedia.org/wikipedia/commons/8/85/Git_branches_example.png https://upload.wikimedia.org/wikipedia/commons/9/99/Highway_at_night_slow_shutter_speed_ph otography_02.jpg https://c2.staticflickr.com/6/5058/5490790304_dc3d7c2b91_z.jpg

Add a comment

Related presentations

Speaker: Matt Stine Developing for the Cloud Track Marc Andressen has famou...

This presentation explains how to develop a Web API in Java using (JAX-RS or Restl...

1 App,

1 App,

November 10, 2014

How to bring innovation to your organization by streamlining the deployment proces...

Cisco Call-control solutions can handle voice, video and data

Nathan Sharp of Siemens Energy recently spoke at the SAP Project Management in Atl...

Related pages

IBM developerWorks : DevOps : Technical library

Filter by products, topics, and types of content IBM product :
Read more

IBM developerWorks : Rational : Technical library

Browse the Rational technical library view for technical articles, IBM Redbooks, and tutorials. View the list by product, title, topic, ...
Read more

Business Architecture | The Open Group Blog

Posts about Business Architecture written by The Open Group Blog. ... (EA) perspective, ... Rational User Conference, ...
Read more

ArchiMate | The Open Group Blog | Page 2

Posts about ArchiMate written by The Open Group Blog. ... This will allow creating the right alignment from Business Perspective and will ... then EA may ...
Read more

Rational Clearcase. | LinkedIn

View 13175 Rational Clearcase. posts, presentations, experts, and more. Get the professional knowledge you need on LinkedIn. LinkedIn Home What is LinkedIn?
Read more

Design and implementation of a social networking platform ...

The Erratum to this article has been published in Journal of Internet Services and Applications ... or groups that may interest a user. ... May 2014 about ...
Read more