Software development organizations that have implemented ITIL or one of its variants often ask me how the framework will be phased out as we start implementing DevOps processes. A few organizations have started taking steps to do away with ITIL framework without due diligence from a DevOps perspective. In the case
Process development and implementation is a skill that is best learnt through experience and maturity. Organizations implementing ITIL processes normally develop workflows, define activities, identify roles and embed all of it in a process document. This is good, but there is a major chunk that is still missing. The design.
Last week, I took you on a journey into the world of ITIL processes. It is exciting to play with processes, isn't it? Today, I am going to divulge the characteristics of what makes a process complete and objective based. Remember that the following characteristics are common across all ITIL processes. Popularly in
ITIL is layered on the concept of processes and functions. You need to understand the concept, similarities and the differences between the two to become ITIL foundation certified. Functions are like the specialized teams you have in organizations. To give a few examples: Java team Network team Unix team Database team These