Change Management for non-prod environments

[Richard9]

Have your organization implemented or used changed management to manage changes for non-prod environments?  I have never implemented ITSM lean for non-prod environments before.  We are assessing if change management is a good fit or is there a better product or approach?

The goal here is to overcome the challenges of managing complex non-production environments and to ensure that changes are conducted correctly and delivered in a consistent manner.  Non-prod changes will consist of both hardware and software changes.

Any feedback would be appreciated.

Thanks,

[Kirsten3]

Why have 799 people reviewed this question but not a single person has responded. I also would like to get some advice on whether or not it should be mandatory to raise normal changes for non-production environments and not supported by the ITSD and would not be impacted by a P1 or P2 major incident

[Chris Greenham]

Although not standard practice, controlled RFCs can be created for Non-Production (Non-Prod) changes to improve visibility and control. CRs should be raised as standard, with the environment set to Non-Prod.

P1 and P2 performance reporting should exclude Non-Prod RFCs to ensure KPIs reflect only Production changes.