Speed Your Apps Launch to Market: Learn Six Best Practices for DevOps

1,408 views

Published on

Today’s pace of business and competitive pressures are driving organizations to constantly release new applications and features. Organizations are embracing the concept of DevOps to enable apps to be designed, developed and deployed more quickly, at lower cost and with fewer problems. New technology and best practices can help propel organizations towards a successful DevOps model.

Join featured industry experts from Forrester Research Inc. and Compuware dynaTrace to learn:
• Six Steps IT Ops Can Take To Build A Tighter Relationship With Development Groups
• How to identify hidden dependencies and unforeseen risks
• Overview of current and future tools used in DevOps environments

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,408
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Speed Your Apps Launch to Market: Learn Six Best Practices for DevOps

  1. 1. ^ z > D > ^ W K d W D K ^ Z Z d ^ d
  2. 2. Improve Business Services with DevOpsGlenn O’Donnell, Senior AnalystOctober 27, 20112 © 2011 Forrester Research, Inc. Reproduction Prohibited 2009
  3. 3. What is DevOps?A movement to improve collaboration New demands accelerate need for collaboration Service lifecycle is broken peace Make Code Dev Ops don’t get along /peace DevOps To Not War The People3 © 2011 Forrester Research, Inc. Reproduction Prohibited
  4. 4. Why DevOps is SkyrocketingComplexity and economics mandate a new model Technology is too complex – Virtualization and cloud – Social media and Mobility – Agile application development Time frames are accelerating Agile Dev Lethargic processes kill innovation Traditional IT is economically dead Business demands better Virtualization4 © 2011 Forrester Research, Inc. Reproduction Prohibited
  5. 5. Stereotypes Fuel Conflict • Slow to act • Impatient • Temperamental • Temperamental • Too rigid about changes • Careless about changes • Always says “No!” • Prima donna artists • Too dumb to understand apps • Ignorant about the “real world”5 © 2011 Forrester Research, Inc. Reproduction Prohibited
  6. 6. How to Make DevOps Work Measure Talk! Accept and hide complexity but don’t love it ( talk!) Embrace process discipline across the lifecycle ( talk!) Start with a common release management process ( talk!) Automate release management execution ( talk!) Inject rich feedback across the lifecycle ( talk!) Change the incentives ( talk!) Adapt the organization(s) ( talk!) Measure ( talk!)6 © 2011 Forrester Research, Inc. Reproduction Prohibited
  7. 7. Agile Process Adoption Continues To Advance Iterative: 2010 – 19.5% 2009 – 20.6% Traditional: 2010 – 13.0% 2009 – 13.4%Base: †1023 IT ProfessionalsBase: *1298 IT Professionals(“other” responses not included; percentages may not total 100 because of rounding) Source: †Forrester/Dr. Dobb’s Global Developer Technographics® Surveys, Q3 2010 *Forrester/Dr. Dobb’s Global Developer Technographics® Surveys, Q3 2009 7 © 2011 Forrester Research, Inc. Reproduction Prohibited Source: January 20, 2010, “Agile Development: Mainstream Adoption Has Changed Agility” report
  8. 8. It Takes Too Long to Release Apps February 2011 “Five Ways To Streamline Release Management”8 © 2011 Forrester Research, Inc. Reproduction Prohibited
  9. 9. … And People Aren’t Happy About It February 2011 “Five Ways To Streamline Release Management”9 © 2011 Forrester Research, Inc. Reproduction Prohibited
  10. 10. Agile Development Must Meet Agile OperationsTraditional Leaving Welcome ToTransition Dev Ops Come Back Soon! Drive Safe! Release Management is Too SlowAgile Leaving Welcome ToTransition Dev Ops Come Back Soon! Drive Safe! 10 © 2011 Forrester Research, Inc. Reproduction Prohibited Streamlined Release Management
  11. 11. The Typical Application Life Cycle is Broken Ops App EA Dev QA Ops One-way flow doesn’t allow for continual improvement Information developed early is lost when given to Ops – Ops must resort to reverse engineering (a wasteful effort) Release from App Dev to Operations is a huge problem – Thus, also a huge opportunity Cultural barriers must fall but tools must also evolve – New tool developments are promising11 © 2011 Forrester Research, Inc. Reproduction Prohibited
  12. 12. Collaborate Across The Application Life Cycle App EA Dev QA Ops Agile Process Feedback makes it a true lifecycle with continual improvement Automation based upon apps span the lifecycle – Apps become adaptive like infrastructure now is Information is preserved and put to good use everywhere A well-managed portfolio emerges from people communicating!12 © 2011 Forrester Research, Inc. Reproduction Prohibited
  13. 13. Packaging Releases Move packages, not individual components Development Staging Production Transitions of Components Package Transitions of a Package13 © 2011 Forrester Research, Inc. Reproduction Prohibited
  14. 14. “Fast and Accurate” Need Not Be a Paradox “Process = Bureaucracy” is a misconception Discipline becomes oppressive only if taken too far Good process enhances agility Automation further accelerates execution14 © 2011 Forrester Research, Inc. Reproduction Prohibited
  15. 15. Automation Must Evolve Beyond Infrastructure It’s finally time to focus on the applications Automation is almost entirely aimed at infrastructure “Cloud” is mainly IaaS PaaS SaaS cannot be limited to infrastructure Infrastructure is commodity Applications are not (yet) Business flexibility is the goal – Automation must move “up the stack”15 © 2011 Forrester Research, Inc. Reproduction Prohibited
  16. 16. Cloud Introduces NoOps to Augment DevOpsRqmts Dev App QA App Ops App Application Deployment to Traditional Infrastructure (DevOps)Rqmts Dev App QA App Application Deployment to IaaS Infrastructure (NoOps)Ops becomes key to planning, not to release execution16 © 2011 Forrester Research, Inc. Reproduction Prohibited
  17. 17. A Lifecycle Fosters Systems Engineering Apps are complex products All product development follows sound engineering principles Why should IT services be any different? – Including apps Software engineering ≠ writing code Infrastructure engineering ≠ hardware silos ITIL v3 offers a good starting point for engineering lifecycle – ITIL is not just for Ops anymore17 © 2011 Forrester Research, Inc. Reproduction Prohibited
  18. 18. Change the Incentives You need the right carrot and right stick to alter behaviors The IT culture rewards the techno-heroes – Reward the firefighter; reward the arsonist – Discourages teamwork Complexity mandates team execution New metrics for performance should focus on: – Business performance (What’s my impact?) – Team success (overall productivity and service quality) Link bonuses and other incentives to these metrics – And give them teeth (don’t be meek about penalties) Encourage prudent risk to encourage innovation – Allow people to fail so they don’t become failures18 © 2011 Forrester Research, Inc. Reproduction Prohibited
  19. 19. What Metrics Matter (and why)? APM (Response Time) Successful releases Customer satisfaction19 © 2011 Forrester Research, Inc. Reproduction Prohibited
  20. 20. Summary DevOps is about changing organizational philosophies Abandon the stereotypes of all parties Talk! Abandon the love affair with complexity Streamline the handoff from Dev to Ops (agile lifecycle) Get serious about process discipline, but don’t go too far! Drive toward “NoOps” if you pursue cloud Think beyond infrastructure as you pursue cloud Institute systems engineering practices across the entire lifecycle20 © 2011 Forrester Research, Inc. Reproduction Prohibited
  21. 21. Thank youGlenn O’Donnell+1 617.613.8826godonnell@forrester.com @glennodonnellwww.forrester.com © 2009 Forrester Research, Inc. Reproduction Prohibited
  22. 22. Core Strategies forSuccessful DevOpsAlois Reitbauer, Technology Strategist 22 © 2011 Forrester Research, Inc. Reproduction Prohibited
  23. 23. We accelerate development, butdo we accelerate business? 23 © 2011 Forrester Research, Inc. Reproduction Prohibited
  24. 24. If you are agile you will makemore mistakes quicker … … with DevOps you can also fix them faster.24 © 2011 Forrester Research, Inc. Reproduction Prohibited
  25. 25. More than Dev and Ops …25 © 2011 Forrester Research, Inc. Reproduction Prohibited
  26. 26. Integrated Business Continuous aware Successful DevOps is … Application Actionable Centric Automated26 © 2011 Forrester Research, Inc. Reproduction Prohibited
  27. 27. Business Aware27 © 2011 Forrester Research, Inc. Reproduction Prohibited
  28. 28. User Experience comesfirst 28 © 2011 Forrester Research, Inc. Reproduction Prohibited
  29. 29. Canon has the longest search timesOperations must becomebusiness aware and makes 50 perceont of revenue 29 © 2011 Forrester Research, Inc. Reproduction Prohibited
  30. 30. Operations has to focus onbusiness delivery 30 © 2011 Forrester Research, Inc. Reproduction Prohibited
  31. 31. Test ProductionBusiness as a commonlanguage Development 31 © 2011 Forrester Research, Inc. Reproduction Prohibited
  32. 32. Transaction Centric32 © 2011 Forrester Research, Inc. Reproduction Prohibited
  33. 33. PostOrder RemoteAPI ApplyCredit Order eBiz Fraud PriceCalc GiftCard Batch MyMart Associate eBillme Response Clearance 100.000s users MyAppr StoreLocator LoyaltyInfrastructure is PurchaseTrk Layaway SSOcomplex and lacks Stores Paypalcontext 33 © 2011 Forrester Research, Inc. Reproduction Prohibited
  34. 34. Search PaymentEvery transaction isdifferent Login 34 © 2011 Forrester Research, Inc. Reproduction Prohibited
  35. 35. ^Identify core businesstransactions 35 © 2011 Forrester Research, Inc. Reproduction Prohibited
  36. 36. , ^Enrich with metadata 36 © 2011 Forrester Research, Inc. Reproduction Prohibited
  37. 37. , ^ Z d Z d , , Implement transactional ^ Zmonitoring D D 37 , © 2011 Forrester Research, Inc. Reproduction Prohibited
  38. 38. Proactive38 © 2011 Forrester Research, Inc. Reproduction Prohibited
  39. 39. Regression AnalysisMonitor AutomaticallyActionable FeedbackDevelopment Data 39 © 2011 Forrester Research, Inc. Reproduction Prohibited
  40. 40. Continuous Tracking inDevelopment 40 © 2011 Forrester Research, Inc. Reproduction Prohibited
  41. 41. Notify about changes and not only problems Performance regression problem detectedContinously TrackPerformance Trends 41 © 2011 Forrester Research, Inc. Reproduction Prohibited
  42. 42. Actionable Information 42 © 2011 Forrester Research, Inc. Reproduction Prohibited
  43. 43. A DevOps solution … delivers business insight understands applications integrates into lifecycle provides actionable data accessible in real time43 © 2011 Forrester Research, Inc. Reproduction Prohibited
  44. 44. Alois Reitbauer Technology Strategist alois.reitbauer@dynaTrace.com @AloisReitbauer blog.dynaTrace.com44 © 2011 Forrester Research, Inc. Reproduction Prohibited
  45. 45. Questions Answers45 © 2011 Forrester Research, Inc. Reproduction Prohibited 2009

×