change record final status

[gon689]

Hello... I am looking for some advise...

In accordance, with our change mgmt process, once a change has been implemented, the change record must updated with its final status.

Here are the final statuses and their description:

Completed - A change has been fully implemented into production & successfully verified within the specified Change Window.

Backedout - Once the Actual Start date & time have been reached, “Backedout” status must be used when a change has been implemented and subsequently backed out (100%) of production within the Change Window, or when it has not been attempted at all for a valid reason. The Change Owner must enter the reason the change was Backed Out in the Update field.

Completed with Issues - A change which has not been completed successfully and which has not been fully backed out (100%) within the scheduled change window. The Change Owner must enter the reason the change Completed with Issues in the Update field.

We have a situation, where a system change was implemented with some functionalities not working properly. The business users were aware of this and agreed to the implementation anyways.

Should we consider this change successful or "completed with issues"?

Thank you in advance.

[asrilrm]

Hi,

It would depend on how we individually see status and what it would give us.
For me, final status is boolean, successful (or completed, etc.) or failed (with or without backout). Before that, you could have "completed with issues", "pending", "in progress", or anything as interim status.

To your question from my logic, it's still an open RFC with interim status "in progress". It's not successful (yet) nor failed.

Cheers,
Asril