In my todays article I’d like to give some argues about: what is DevOps, what is it not – and how to combine or compare with ITIL.
DevOps is often seen as a group of people doing new cloud stuff. ITIL is seen as a bunch of slow processes.
So let’s first have a definition of both:
DevOps is often seen as a group of people doing new cloud stuff. ITIL is seen as a bunch of slow processes.
So let’s first have a definition of both:
ITIL (formerly an acronym for Information Technology Infrastructure Library) is a set of detailed practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business. (https://en.wikipedia.org/wiki/ITIL)
1. ITIL Service Strategy: understands organizational objectives and customer needs.
2. ITIL Service Design: turns the service strategy into a plan for delivering the business objectives.
3. ITIL Service Transition: develops and improves capabilities for introducing new services into supported environments.
4. ITIL Service Operation: manages services in supported environments.
5. ITIL Continual Service Improvement: achieves services incremental and large-scale improvements.
2. ITIL Service Design: turns the service strategy into a plan for delivering the business objectives.
3. ITIL Service Transition: develops and improves capabilities for introducing new services into supported environments.
4. ITIL Service Operation: manages services in supported environments.
5. ITIL Continual Service Improvement: achieves services incremental and large-scale improvements.
With the goal of consistency, service quality, customer satisfaction and drivers digital transformation.
DevOps is a methodology that combines software development (Dev) with information technology operations (Ops) with frequently alignment with business objectives. (https://en.wikipedia.org/wiki/DevOps)
1. DevOps integrates software development with testing, QA and operations to achieve better collaboration among product, ops and dev teams.
2. Using Continuous Integration and Delivery tools (CI/CD)
3. Align with lean principles like Work in Progress (WIP), Batches, being agile to have a shorter time to market
4. Cultural transformation
2. Using Continuous Integration and Delivery tools (CI/CD)
3. Align with lean principles like Work in Progress (WIP), Batches, being agile to have a shorter time to market
4. Cultural transformation
Everything we see here is about
- Communication
- Collaboration
- Agility
- Efficiency
- Speed
- Align IT with business
That doesn’t sound like competition or?
Another view:
ITIL is considering the whole environment as once – as a service-silo with dependencies, reduced to tickets and changes. That sounds like a vertical approach.
DevOps is the responsibility of a certain function or feature from development to testing to operations but disconnected from the environment – it is a horizontal approach.
Myths and Facts:
ITIL and DevOps are complementary approaches
ITIL and DevOps are often seen as alternatives – each with his own myths. But in fact, they get along well with each other as their objectives are totally different.
Companies would be doing service management in some way and ITIL helps in streamlining such processes whereas DevOps leverages service delivery by bringing relevant teams together and automating routine tasks to be agile.
DevOps is only about Software development
Many people say: that’s about software development and delivery. But DevOps is much bigger.
DevOps is about collaboration, behavior, thinking outward – we encourage our people to adopt these principles to all our Cloud activities. You can easily exchange software-development to any other kind of IT project – think about BIG Data: how to ingest new data, transform, deploy new models – or Analytics/Data Science – using different algorithm, libraries and tools. DevOps is a method to work in short development/research cycles, adopting learnings immediately and try different versions of your ideas against real data/customer data.
DevOps is a cross disciplinary method to drive innovation.
Software development is just one environment to adopt DevOps methods. And it follow a classic IT approach. It strives cross-disciplinary training so that everybody has a basic understanding of every task.
ITIL – only for Enterprises
If is a myth, that ITIL is always complex, slow and expensive – too expensive for smaller businesses. But ITIL is independent of the company size. ITIL can be very flexible as long as you are using suitable processes. You can start ITIL small und implement only relevant/necessary processes and increment on demand. The problem with many ITIL implementation is, that they are build up very complex to cover any aspect of demand. To find a suitable process which serves fast and agile demands on rapid changing technologies is therefor hard to implement.
If the process doesn’t fit to ITIL – then it becomes hard, slow, expensive. The implementation and tools of ITIL is the main driver for that – not the size of the company or ITIL definition by itself.
DevOps is just automation
DevOps is neither a tool nor an automation. It is a methodology to has automation as a result by identifying gaps and collaborating within DevOps teams how to solve gaps or reoccurring errors just by learning and automation. Automation also can lead just into new monitoring aspects and will make operational inconsistence transparent.
ITIL & DevOps implementation is expansive
No matter what you implement, it will lead to a reduction of cost and resources you need to dive digitization and operation. When the right tool is implemented for the right business, time-2-market is being accelerated. To combine both methods, DevOps needs to serve the right process/interfaces from ITIL – then you can create agile environment by having a high secure/predictable cloud environment, serving services on high SLA. The right identity and access management is crucial to offer DevOps people the tools to work on these environments without disturbing the ITIL process environment.
DevOps is the responsibility of a certain function or feature from development to testing to operations but disconnected from the environment – it is a horizontal approach.
Myths and Facts:
ITIL and DevOps are complementary approaches
ITIL and DevOps are often seen as alternatives – each with his own myths. But in fact, they get along well with each other as their objectives are totally different.
Companies would be doing service management in some way and ITIL helps in streamlining such processes whereas DevOps leverages service delivery by bringing relevant teams together and automating routine tasks to be agile.
DevOps is only about Software development
Many people say: that’s about software development and delivery. But DevOps is much bigger.
DevOps is about collaboration, behavior, thinking outward – we encourage our people to adopt these principles to all our Cloud activities. You can easily exchange software-development to any other kind of IT project – think about BIG Data: how to ingest new data, transform, deploy new models – or Analytics/Data Science – using different algorithm, libraries and tools. DevOps is a method to work in short development/research cycles, adopting learnings immediately and try different versions of your ideas against real data/customer data.
DevOps is a cross disciplinary method to drive innovation.
Software development is just one environment to adopt DevOps methods. And it follow a classic IT approach. It strives cross-disciplinary training so that everybody has a basic understanding of every task.
ITIL – only for Enterprises
If is a myth, that ITIL is always complex, slow and expensive – too expensive for smaller businesses. But ITIL is independent of the company size. ITIL can be very flexible as long as you are using suitable processes. You can start ITIL small und implement only relevant/necessary processes and increment on demand. The problem with many ITIL implementation is, that they are build up very complex to cover any aspect of demand. To find a suitable process which serves fast and agile demands on rapid changing technologies is therefor hard to implement.
If the process doesn’t fit to ITIL – then it becomes hard, slow, expensive. The implementation and tools of ITIL is the main driver for that – not the size of the company or ITIL definition by itself.
DevOps is just automation
DevOps is neither a tool nor an automation. It is a methodology to has automation as a result by identifying gaps and collaborating within DevOps teams how to solve gaps or reoccurring errors just by learning and automation. Automation also can lead just into new monitoring aspects and will make operational inconsistence transparent.
ITIL & DevOps implementation is expansive
No matter what you implement, it will lead to a reduction of cost and resources you need to dive digitization and operation. When the right tool is implemented for the right business, time-2-market is being accelerated. To combine both methods, DevOps needs to serve the right process/interfaces from ITIL – then you can create agile environment by having a high secure/predictable cloud environment, serving services on high SLA. The right identity and access management is crucial to offer DevOps people the tools to work on these environments without disturbing the ITIL process environment.
ITIL & DevOps -> This is a complement and NOT a competition!
It is obvious that the basic ideas of ITIL and DevOps are following very similar principles. They have similar roots aiming for better collaboration and higher efficiency. DevOps scope is faster turn-around times and agility through automation. ITIL also focus on automation to improve service quality.The holy grail is to understand the purpose of each of these clearly and implement the right one for the right problem. Then ITIL and DevOps can cooperate within same environments addressing different demands from business.
“ITIL drives DevOps and DevOps improves ITIL”
Keine Kommentare:
Kommentar veröffentlichen