AGILE AND AUTOMATION CONCLAVE 2018

Transcription

1 AGILE AND AUTOMATION CONCLAVE 2018 DevOps adoption prism Vijeth S Hegde

2 Vijeth S Hegde DevOps capability lead

3 3 DevOps Adoption What Do We Need? DevOps & Agile Adoption is not just the technical journey, but it requires cultural change and skill/talent building. True benefits of DevOps are realized when various (below mentioned) dimensions are addressed in DevOps Adoption Journey. Analyze and use the right Dev, Ops & Testing Tools Standardize the tools & processes In case of new development, choose the light weight and Agile friendly technologies, architecture and rapid prototyping Explore the option of Agile infrastructure e.g. virtualized/cloud based environments Start with DevOps Analytics (e.g. Splunk) Mentor/Coach & Build the skills necessary to execute functions in a DevOps way e.g. Test Automation, SCM, Build a culture that support collaboration, high-trust, continuous improvement and continuous experimentation Form the efficient and lean Operating Model Technology & Engineering Tools Enterprise Governance & Metrics People and Organisation & Culture Programme & Change Management DevOps and Agile Practices Start with Lean Governance and setup Governance framework Delivery and thought leadership Setup, baseline Metrics and KPIs to drive Continuous Improvement (by continuous measuring/feedback) Setup Continuous Integration and Deployment practices as hygiene factors for BSS & SMIP Applications Extend the framework to Continuous Delivery Practice and adopt Agile methodology Apply Shift Left, Test Driven Development and Extreme automation for Testing Drive and Manage the DevOps change programme Training/Coaching/Mentoring

4 4 DevOps Adoption Prism - Concept Set of Goals and Overall Commitment for DevOps Adoption 4. Organization Layer 3. Line of Business or IT Division Layer 2. Application Cluster (or Program) Layer Measurable and Identifiable Set of Areas/Practices required for DevOps Adoption 1. Application (or Project) Layer

5 5 DevOps Adoption Prism - Approach Goals Layers What s Needed Become DevOps Organization and be competitive in business and fast changing ecosystem. Drive business with DevOps adoption in its IT. 4. Organization Layer Consolidated Governance Model Across LoBs / IT Divisions Alignment of DevOps with Enterprise Strategy and Architecture Adopt DevOps as a culture at LoB/IT Division level and improve quality, time to market with cost effective s/w development. 3. Line of Business or IT Division Layer DevOps Alignment with other transformations e.g. Agile, Modernization Infrastructure Optimization e.g. Journey to Cloud Effective Stakeholder and Vendor Mgmt, Ownership & Commitment Cultural & Change Management DevOps Analytics and Applying Artificial Intelligence Governance Model (Standardization at Center & Industrialization at lower layers) DevOps Organization structure DevOps-as-a-Service & Self-Service models Multi-tenant & scalable DevOps platform Improve combined DevOps maturity for dependent applications to achieve faster time to market for whole cluster 2. Application Cluster (or Program) Layer Identification of application clusters Consolidated DevOps assessment and implementation plan for effective consolidated releases management & practices Implement DevOps practices to improve quality and time to market of individual application 1. Application (or Project) Layer Selection of right application Assessment and implementation plan of DevOps adoption DevOps tools setup & process design Pilots and quick wins CI/CD implementation and other DevOps practices

6 6 DevOps Adoption Hybrid [centralized and decentralized] Operating Model 4. Organization Layer 3. Line of Business or IT Division Layer Centralized CoE Functions Functions Aligned to Layer 1 and 2 DevOps CoE Other IT and Business Functions 2. Application Cluster (or Program) Layer Application Clusters (or Programs) 1. Application (or Project) Layer Applications (or Projects)

7 DevOps Adoption Prism Factory/CoE Model DevOps-as-a-Service Model is recommended for Clients to reduce the technical debt as well as standardize DevOps adoption and speed-up testing automation. We offer to build *-as-a-service Model by Centralized DevOps Capability. LoBs and Their Projects LoB-1 LoB-2 LoB-3 Projects Projects Onshore Onshore Projects Onshore Offshore Agile Team Offshore Agile Team Offshore Agile Team Overall DevOps Services Define and Build Service Catalogue Estimate, evaluate and associate Work Units for each service and the complexity (high/medium/low) Centralized DevOps CoE / Capability Examples of DevOps Services Catalogue - DevOps-as-a-Service Model Service Complexity Work Unit Effort (Illustrative) Define and associate metrics/kpis for each Service Feedback and Fine Tuning Metrics Publish, Start Serving the requests Build Automation (AEM) Medium 6-8 hours Build Automation Index, % Reduction in Build Failures Measure and Report Metrics/KPIs Deployment Automation (Java) Simple 4-6 hours Deployment Automation Index, % Reduction in Deployment Failures, % Reduction in Deployment Time Setup CI/CD Pipelines (SFDC) Medium 6-8 hours. Supporting Functions QA CoE Infra Sec urity.

8 DevOps Adoption Application Selection Methodology Starting Right is the key to success. This is what we offer from a well-defined and well-structured application selection methodology for choosing right applications for DevOps adoption. A. DevOps Maturity Assessment B. Cost Vs Benefit Analysis C. Choose the Right Applications

9 Q&A

10 Vijeth S Hegde Vijeth.s.hegde@Accenture.com FOLLOW US LinkedIn SolutionsIQ India Twitter SIQIndia Facebook SolutionsIQ India