DevOps, BA and COBIT don’t really align, or do they?

DevOps, BA and COBIT don’t really align, or do they?

• 1.
  IIBA Canberra DevOps and COBITdon’t really align, or do they? March 2019 COMMUNITY EVENT Harold Petersen E: [email protected]
• 2.
  Digital businesses requireagility in Business Systems & Service Delivery • Digital Strategy is Business Strategy, • IoT, AI, Big Data, Platform businesses are fueled by software, • The market requires the same sort of rapid development and UX as what they are used to with ‘apps’, • ‘Time to Value’ instead of ‘Time to Market’. 3 3
• 3.
  ‘Digital’ needs velocity… 5
• 4.
  DevOps benefits • >30,000 survey responses over 5 years, • 1,900 participants in 2018, Demonstrates that DevOps enables: • higher IT performance • improved business outcomes, as measured by productivity, profitability, market share and achievement of broader organisational goals. Elite Performer Metrics (vs Low Performers) • Deployment frequency: On demand (46x more frequent) • Deployment lead time: < 1 hr (2,555x faster) • Mean Time to Recover (MTTR): < 1hr (2,604x faster) • Change Failure Rate: 7.5% (7x lower than low performers) https://cloudplatformonl ine.com/2018-state-of- devops.html 6 6
• 5.
  … I think Isaw it still moving … What about COBIT, BABOK, ITIL, etc ? 7
• 6.
  Agenda • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 8
• 7.
  Agenda • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 9
• 8.
  10 Other(internal/external) SD EUC Comms Hosting Comms Service Strategy Management(CIO & DRs) ICT Strategy, aligned with Business, BRM, Demand, Service Portfolio & Financial Management ICT Service Design & Architecture (ICT Policies, ICT Design standards, EA, SOA) BRMs (Service Modelling, BRM, Service Level Management, Governance & CSI, Communications) New and Existing ICT Service Engagement Business Business Strategy ICT Service Demand BAU Delivery and Support Service Level Achievement Reporting & Management Design, Build, Test, Deploy. Supplier Strategy ICT Management and governance processesBusiness End User Comp Hosting App Mgt SIAM (Service Integration, Supplier SLM, Supplier process KPI control, Supplier Communications, COE) Internal & External SPs Service Operations (Operational Bundle controls, Escalations, Project & Process Assurance, ownership of some processes, contribution to others), Process KPI reporting BA, PMO and Service Transition (Schedule & Control of Plan/Build/Transition) 10 ‘Enterprise ICT’
• 9.
  12 COBIT Core Model
• 10.
  13
• 11.
  14 COBIT Core Model
• 12.
  15 Excerpt of BAI02Management Objectives
• 13.
  16 Process / MgtPractices BAI02
• 14.
  17 Organisational Structure BAI02
• 15.
  18 COBIT Overview 18
• 16.
  Agenda • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 22
• 17.
  Change Owner Reviewers (Tech, Ops,QA, PO) CAB Builders & Implementers Reviewers (Tech, Ops, QA, PO) Submit RFC Approve (Build & Schedule) Review & Sign Off Build & Test Review & Sign Off Authorise (Deploy) Deploy Request Close Review & Accept Close RFCRFCRFCRFCRFCRFCRFCRFC 23 Excerpt of a Change Management workflow (for non-standard, non-emergency changes)
• 18.
  Do we needto choose one or the other? 24 Less risk Faster time to value
• 19.
  Recommended DevOps reading ThePhoenix Project • World famous ‘novel’ about IT Management and DevOps experiences The DevOps Handbook • how to integrate Product Management, Development, QA, IT Operations, and Information Security to elevate your company and win in the marketplace Continuous Delivery • Principles, automation and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users26 26
• 20.
  The three ways Thefirst way – Flow • Understand and increase the flow of work (left to right) The second way – Feedback • Create short feedback loops that enable continuous improvement (right to left) The third way – Continuous experimentation and learning • Create a culture that fosters • Experimentation (taking risks) and learning from failure • Understanding that repetition and practice is the key to mastery 27 27
• 21.
  ’The first way’of DevOps: Understand the entire system and optimise the flow of work from left to right Plan & Design Code & Commit Integrate & Build Test Stage & Deploy Agile Development Continuous Integration Continuous Delivery and/or Deployment 28 28 © North BDT
• 22.
  Deployment pipeline and‘toolchain’ 29 29
• 23.
  ‘The 2nd way’of DevOps: Shorten and amplify feedback loops from right to left Plan & Design Code & Commit Integrate & Build Test Stage & Deploy Agile Development Continuous Integration Continuous Delivery and/or Deployment Continuous Testing 32 32 © North BDT
• 24.
  33 33 Deployment pipelinegateways
• 25.
  Periodic Table ofDevOps tools 34 34
• 26.
  The third way: Continuous experimentation and learning • CSI time allocation • Reward risk taking • Specifically organise safe experimentation and innovation events (eg hackathons) • Deliberately introduce failure to improve resiliency and antifragility (eg chaos monkey) • Repetition and learning is the key to mastery 38 38
• 27.
  Change Models, enabledby people, automation, etc (non- standard, non-emergency changes) Change Owner Reviewers (Tech, Ops, QA, PO) CAB Builders & Implementers Reviewers (Tech, Ops, QA, PO) Submit RFC Approve (Build & Schedule) Review & Sign Off Build & Test Review & Sign Off Authorise (Deploy) Deploy Request Close Review & Accept Close RFC 39
• 28.
  Agenda • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 40
• 29.
  42 Other(internal/external) SD EUC Comms Hosting Comms Service Strategy Management(CIO & DRs) ICT Strategy, aligned with Business, BRM, Demand, Service Portfolio & Financial Management ICT Service Design & Architecture (ICT Policies, ICT Design standards, EA, SOA) BRMs (Service Modelling, BRM, Service Level Management, Governance & CSI, Communications) PMO and Service Transition (Schedule & Control of Plan/Build/Transition) New and Existing ICT Service Engagement Business Business Strategy ICT Service Demand BAU Delivery and Support Service Level Achievement Reporting & Management Design, Build, Test, Deploy. Supplier Strategy ICT Management and governance processesBusiness End User Comp Hosting App Mgt SIAM (Service Integration, Supplier SLM, Supplier process KPI control, Supplier Communications, COE) Internal & External SPs Service Operations (SIAM) (Operational Bundle controls, Escalations, Project & Process Assurance, ownership of some processes, contribution to others), Process KPI reporting BA, PMO and Service Transition (SIAM) (Schedule & Control of Plan/Build/Transition) 42 ‘Enterprise ICT’
• 30.
  43 COBIT Core Model
• 31.
  44 COBIT Overview 44
• 32.
  Agenda • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 45
• 33.
  Have a visionfor the long term, yet iteratively move towards it Interim State 1 Interim State 2 Interim State 3 Business Value 46 46 Long Term Target state
• 34.
  People, Organisation andCulture 47 47
• 35.
  Action based learning/ coaching tool DevOps simulation: The Phoenix Project 50 50
• 36.
  Apply agile principlesto your DevOps/COBIT implementation OCM 1 M ~3 M ~ 3 M ~ Backlog - Introduce, spread and embed DevOps culture - Introduce automation and release policy optimisation for applications - Benefits realisation monitoring & reporting ~3 M Sprints Sprints Sprints Sprints Stage Stage Stage1 M Stakeholder Engagement & Prep Business Value Long Term Target state Current State 51
• 37.
  Summary • COBIT 2019 •DevOps • DevOps and COBIT 2019 • Next steps 52
• 38.
  Next steps? 53
• 39.
  northbdt.com.au DevOps and COBITdon’t really align, or do they? Harold Petersen E: [email protected]