Posted: Thu Feb 01, 2018 12:58 am Post subject: Change become and incident?
Hi all I am trying on the main forum to see if anyone can answer me the age old. When does a change become an incident.
I am having the argument that the change window should cover implementation and back out and any bits in between. If for whatever reason the change window is not suffice and everyone knows that service will not be restored within the given window. Then a decision as to whether an incident can be raised should be discussed and potentially followed through.
Correct me if my understand is incorrect and I am just talking nonsense.
There is a huge difference between Incident and Change.
If something is broken or not working as expected or agreed, is called an incident and should be fixed by providing a workaround or a solution as followed by Incident Management process.
Any modification/deletion in a production environment is a change. Change Management controls the changes where a change is tested in non-production environment, impact assessment is done on the same and dependent CIs, estimated time is calculated to deploy the change, approvals are taken from all the related CI owners, rollback plan is discussed. once all in place, accordingly the change is deployed in production environment within agreed change window while associating with a release window.
Answer to your question: Please discuss with your business representative/Risk manager/Situation manager/Operation Landscape Manger/Component Landscape Manager whoever is available for you. This should be taken as a risk and the change window should be set according to the change.
If change does not go successful, roll-back the change.
If goes partial successful, raise an Incident as defect and follow the same.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum