Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
Agile and Automation Conclave 2018
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.
Enterprise Governance& Metrics
People and Organisation& Culture
Technology & Engineering Tools
DevOps and AgilePractices
Programme & Change Management
• 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
• 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 skillsnecessary 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
Agile and Automation Conclave 2018
4
Set of Goals and Overall Commitment for DevOps Adoption
Measurable and Identifiable Set of Areas/Practices required for DevOps Adoption
4.Organization
Layer
3.Line of Business or IT
Division Layer
2.Application Cluster (or Program) Layer
1.Application (or Project) Layer
DevOps Adoption Prism - Concept
Agile and Automation Conclave 2018
4.Organization
Layer
3.Line of Business or IT
Division Layer
2.Application Cluster (or Program) Layer
1.Application (or Project) Layer
5
• 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
• Identification of application clusters• Consolidated DevOps assessment and implementation plan for
effective consolidated releases management & practices
• Governance Model (Standardization at Center & Industrialization at lower layers)
• DevOps Organization structure• DevOps-as-a-Service & Self-Service models• Multi-tenant & scalable DevOps platform
• Consolidated Governance Model Across LoBs / IT Divisions• Alignment of DevOps with Enterprise Strategy and Architecture
DevO
ps Alignm
ent with other transform
ations e.g.
Agile, M
odernization
Infrastructure Optim
ization e.g. Journey to Cloud
Cultural &
Change M
anagement• Implement DevOps practices to
improve quality and time to market of individual application
• Improve combined DevOps maturity for dependent applications to achieve faster time to market for whole cluster
• Adopt DevOps as a culture at LoB/IT Division level and improve quality, time to market with cost effective s/w development.
• Become DevOps Organization and be competitive in business and fast changing ecosystem. Drive business with DevOps adoption in its IT.
Goals What’s NeededLayers
Effective S
takeholder and Vendor M
gmt,
Ow
nership & C
omm
itment
DevO
ps Analytics and A
pplying
Artificial Intelligence
DevOps Adoption Prism - Approach
Agile and Automation Conclave 2018
Centralized CoE Functions
Functions Aligned to Layer 1 and 2
DevOps CoE
Other IT and Business Functions
4. Organization
Layer
3.Line of Business or IT
Division Layer
2.Application Cluster (or Program) Layer
1.Application (or Project) Layer
6
Application Clusters (or Programs)
Applications (or Projects)
DevOps Adoption – Hybrid [centralized and decentralized] Operating Model
Agile and Automation Conclave 20187
DevOps Adoption Prism – Factory/CoE Model
Examples of DevOps Services Catalogue -
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.
OnshoreOffshore
Agile Team
Overall DevOps Services
LoBs and Their ProjectsCentralized DevOps CoE /
Capability
DevOps-as-a-Service Model
Define and Build Service
Catalogue
Estimate, evaluate and associate Work Units for
each service and the complexity
(high/medium/low)
Define and associate metrics/KPIs for
each Service
Publish, Start Serving the
requests
Measure and Report
Metrics/KPIs
Service Complexity Work Unit Effort (Illustrative)
Metrics
Build Automation (AEM) Medium 6-8 hours Build Automation Index, % Reduction in Build Failures
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 ….
Feedback and Fine Tuning
QACoE
Supporting Functions
ProjectsLoB-1
OnshoreOffshore
Agile Team
ProjectsLoB-2
OnshoreOffshore
Agile Team
ProjectsLoB-3
Infra
Security
….
Agile and Automation Conclave 2018
DevOps Adoption – Application Selection Methodology
A. DevOps Maturity Assessment B. Cost Vs Benefit Analysis C. Choose the Right Applications
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.
Agile and Automation Conclave 2018
FOLLOW USLinkedIn – SolutionsIQ India | Twitter – SIQIndia | Facebook – SolutionsIQ India
Vijeth S [email protected]