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.
I got a proposition from one of my customers. They wanted to have a single database containing asset and configuration details. In other words, they wanted to merge the asset database (ADB) and the configuration management database (CMDB). It is said that databases must be the single source of truth. So,
Business models are fast changing. They no longer employ a single IT service provider for all their IT needs. Instead, IT responsibilities are shared between multiple suppliers, for example networks outsourced to Supplier A, infrastructure and datacenters to Supplier B and application support to Supplier C. In these scenarios, Plain
Change management is a crucial governance ITIL process that sits as the gatekeeper for all changes going into services. This process needs careful consideration in terms of the process definition and implementation. These stages of architecting the process are taken care by the process owner. However, it is the accountability
DevOps is a combination of two words – development and operations. When these two areas of IT are amalgamated, you literally get DevOps. There is a whole lot more to it than meets the eye!
DevOps is just not a nomenclature to refer to the development and the operations in a single vein. It is a change in organizational culture, transformation of processes, and leveraging on technology to speed up software development.