This Webinar will discuss and provide you a sighted approach towards ITIL process improvement. ITIL processes if used as a basis for a DevOps Organizations would give greater focus and help Identify the pain points. Mitigating these challenges in compliance with regulation and frameworks such as ITIL and DevOps would be mutually beneficial. Agenda • Why DevOps? • Fundamentals of DevOps & Agile • Comparison between ITIL and DevOps & Agile • Change in approach using DevOps • How to adapt ITIL processes with DevOps concept; Example - Release management - Change management • Organizing Teams • Q & A

1. Presents Webinar on:
Adding agility to ITIL processes
using DevOps

2. Vyom Labs Overview
 Vyom Labs proudly works with the purpose of ‘Enabling organizations to Align
IT with Business for maximizing value.’
Founded In:
Head Quarters:
Geographic Spread:
End-to-end Offerings:
Key Partnerships:
Key Certification:
2003
Pune, India
30+ Countries
Consulting, Products and Education
BMC, Oracle, EXIN, APMG, ISACA
ISO 20000
Vyom Labs HQ
Pune, India
www.vyomlabs.com

3. Disclaimer
 All other trademarks, service marks and logos used in this Webinar are the
trademarks, service marks or logos of their respective owners.
 The views expressed in this Webinar are views of the speakers and do not
necessarily reflect the views of Vyom Labs Pvt. Ltd.
www.vyomlabs.com

4. Acknowledgement
 ITIL® is Registered Trade Marks of AXELOS Limited.
 IT Infrastructure Library® is a Registered Trade Mark of AXELOS Limited.
 COBIT® is a trademark of ISACA® registered in the United States and other
countries.
www.vyomlabs.com

5. Agenda





Why DevOps?
Fundamentals of DevOps & Agile
Comparison between ITIL and DevOps & Agile
Change in approach using DevOps
How to adapt ITIL processes with DevOps concept; Example
o Release management
o Change management
 Q&A
www.vyomlabs.com

6. Basics First
www.vyomlabs.com
Source: Gartner
(Dec 2012)

7. Why DevOps?
• Traditional best practices need
to be enhanced to meet
business dynamics And agility
needs of today
• Risk avert frameworks seem to
be inefficient
• We need new and reliable ways
of handling the scale and agility
requirement
www.vyomlabs.com

8. DevOps & Agile : Fundamentals
 DevOps = Development + Operations
Requirement management
Service management
Technical aspect





Lean principle – reduce waste
Reduces risks and increases agility
Keep it simple
Build multi skilled teams
Use automation
www.vyomlabs.com

9. ITIL & DevOps Comparison
ITIL
•
•
•
•
•
•
Static body of knowledge
Focus on processes
Technology independent
Regulated
Long established
Mostly ignores software
development
www.vyomlabs.com
DevOps
• Dynamic body of
knowledge
• Focus on concepts
• Embrace Technology
• Not Regulated
• Relatively New
• Embrace software
development

10. Change in Approach using DevOps
Process Design
 Maximize simplicity
Things should be as simple as possible
 Maximize consistency
An aspect of simplicity (Standardization)




Focus on the 80%
Don’t compromise on security
Allow for Continual Improvement
Explore possibilities of sprints
www.vyomlabs.com

11. Change in Approach using DevOps
 People involvement
People who have stake in the outcome must be involved in the effort to
implement an ITIL process
They should
 Be actively engaged
 Help identify the obstacle, implications and actions to be addressed
 Assist in address the challenges
 Help identify critical success factors
They need
 To be empowered
 To be listened to
www.vyomlabs.com

12. What if ITIL is de facto




Cant think of incremental releases?
Everything is important (not only 80%)
Very low risk tolerance
Does this mean that we will be ITIL snails?
 There are many opportunities to add agility to existing high risk sensitive
environments ..you have to just change the perspective
www.vyomlabs.com

13. Example
Release Management
Change Management

14. Release Management
 Clearly define and communicate what should be provided from upstream
Service Design (Service Design Package)
 Make use of Release and Deployment Models
 Prioritize releases based on Business requirements and impact
 Build realistic release schedules that have sufficient padding – set realistic
expectations
 Metric: Average time it takes to deploy a release by priority
 Metric: Average time it takes to deploy a release by release model
www.vyomlabs.com

15. Change Management
 Maximize the number of standard changes
 Ensure the Change Management is represented in early stages of service
lifecycle
 Place responsibility of creating the change record on the person who is most
familiar with the change
 Have approvers review changes before CAB meetings to keep the meetings as
short as possible
 For the CAB, represent the changes in different ways for different audiences
 Metric: Average time it takes to review and evaluate the change
www.vyomlabs.com

17. Key Partnerships
Other Key
Partnerships
www.vyomlabs.com

18. Thank You!
Email
: info@vyomlabs.com
Website : www.vyomlabs.com
www.vyomlabs.com