Factors regarding Change in ITIL and SCRUM

“There is nothing permanent except change.” – Heraclitus, Greek Philosopher.

The Only Thing That Is Constant Is Change - Heraclitus, Greek Philosopher

A lot about life can be summarized from the above statement. When compared with our day-to-day lives, we are always sensitive to change and some persons look upon change as a negative influence on their lives, while the optimistic person feel that the change factor will have a positive result.

Professionals and Organizations are investing in additional certifications such as ITIL Certification, PMP Certification and SCRUM Certification not only for gaining expertise in their domain area but also for creating a more conducive environment, where they can make their projects successful.

Now let us see the differences of Change Management between SCRUM and ITIL:

Change Management in ITIL:

Change Management comes in Service Transition phase of the ITIL Service Lifecycle. Its main purpose is controlling the lifecycle of all to-be changes, and to enable the changes which will be beneficial to the project to be implemented or completed with least disruption to the existing IT services.

Responding to the ever-changing needs of the customer in accordance with the business and request-for-change related to IT as well as ensuring that all the changes are recorded and evaluated and the changes that are authorized by the concerned department (such as Change Advisory Board or Emergency Change Advisory Board)  are done as per the prioritization, planning, testing and implementation. They should also be documented as well as reviewed in a controlled manner are some of the objectives of Change Management in ITIL.

The Change Management in Service Transition stage of ITIL concerns all changes that include every type of architecture, tools, processes, metrics and documentation and also the changes concerned with IT services and other configuration items. The importance of change management is that it is mandatory that all changes are recorded and proper management should emphasized.

Change in SCRUM:

Similar to the change explained above in ITIL, changes in SCRUM will be as follows:

It is mandatory that all the team members in a project should have the basic knowledge and understanding that the development processes implemented according to SCRUM are aimed for change. A project can become successful if the Organization creates awareness in its staff such as maximization of benefits as a result of change management. There could have been negative impacts caused in the initial stages as a result of implementing SCRUM, but explaining the facts in a way which could minimize the adverse atmosphere by means of meticulous processes in Change Management in accordance with SCRUM principles could lead to a positive outcome.

One of the advantages of SCRUM is acknowledging the different changes that can arise in the minds of customers or stakeholders or users regarding their needs. Foremost among its best principles is that it is very difficult for a stakeholder to explain all their requirements in the initial stages of a project.

A Change is always welcomed by SCRUM by means of short Sprints which tend to reflect feedbacks of customers on each and every Sprint deliverables. By this method, a customer has the option to interact regularly with the concerned SCRUM team members, review the deliverables that are ready and make changes in the requirements if they are needed in the next Sprint.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>


Get every new post delivered to your Inbox

Join other followers