As you study for the Project Management Professional (PMP)® exam or even during your practice as a PMP® credentials holder, you may end up questioning if a change request is required when a defect is found in a project. That seems like a complex question but has a very simple
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,
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.
As discussed in the change management introduction post, standard changes are low on risk and impact meter. They are routine changes which have been implemented a number of times. The probability of these changes failing is very low, and even if it fails, the probability of it causing a considerable
Changes that are rate low on risk and low impact are categorized as standard changes. Examples include database re-indexing, minor patch upgrades, and blacklisting of IP addresses. These are merely examples to aid in understanding the standard changes, and every type of organization assesses risks differently. For a charity organization, most minor