Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: Niki1Kmekly
New Today: 18
New Yesterday: 31
Overall: 231522

People Online:
Visitors: 124
Members: 0
Total: 124



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

NOTE: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Prod vs Non-Prod
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Prod vs Non-Prod

Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message

Joined: Jul 15, 2009
Posts: 42
Location: United States

PostPosted: Fri Nov 04, 2011 6:59 am    Post subject: Prod vs Non-Prod Reply with quote

I'm sure this has been discussed so my apologies if I am rehasing a conversation but could not locate one.

We are in the midst of a discussion between change management and a functional group on this. Here's a quick summary:
Change Group:
-Believes that the changes against non-production environments should be treated no differently

Functional Group:
-Believes that all non-production environment changes are low impact changes

I will say that amongst our group (change management) that there is a bit of a differing opinion. The manager believes that we should have a separate workflow for anything non-production as the CAB would not care about non-production. The staff in the change team that has been around for a while sees this a bit more black and white. Mind you that all we are talking about is the infrastructure side of the world as the application side in this scenerio have a uniquely separate change and release process.

I'm curious how others manage the differences with the environments and the way they progress through your workflows.[/list]
Back to top
View user's profile
Senior Itiler

Joined: Sep 16, 2006
Posts: 3597
Location: London, UK

PostPosted: Fri Nov 04, 2011 6:34 pm    Post subject: Reply with quote

It depends

The way it is done where I am is as follows

All non production systems and applications are controlled / owned by the Release Manager. The RM ensures that the enviroments - Projects and Support - are available for use to the users in question - programmers, project teams, etc. The Environments manager makes sure that the system / application / environment when delivered is configured based on the defined requirement for the purpose. Once delivered, the RM takes over

All non production system, applications, service, database work and other related work must be filtered / approved / acknowledged / inform the Release Manager. All down time has to be agreed by the RM - who seeks the environment user owner acquiesence /acknowledgement.

As patch management, deployment management and all related activities are within scope of RM process, all activity in non production falls under the RM

if a system has not been delivered, the RM does not care - unless the work impacts any existing system, application, service or database.

Change Management does the same for all production and DR systems as these are Production.

The CM depends on the RM process to be followed

And having said that, incident management and fault resolutions where systems require reboots / restarts to restore services are handled as incident activities - within reason. If the service is down and a reboot is needed to restore - restore service. If the service is up but a reboot is needed to solve an outstanding incident.... schedul and approve
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile

Joined: Jul 09, 2009
Posts: 15

PostPosted: Sat Nov 05, 2011 4:59 am    Post subject: Reply with quote

Where I work:

- Test bed changes are categorised to be low on impact & Risk. However, that doesn't make these changes as standard or no impact change. So they go through the change management cycle.
- These changes are discussed in a meeting (call it a CAB for these servers) and participants are those present in regular CAB except business guys. They have never shown their willingness to join (it doesn't matter to them)

I am also aware of a place where non production & production environment are treated as different customers having a trust relationship.
Back to top
View user's profile

Joined: Oct 26, 2005
Posts: 4

PostPosted: Thu Nov 10, 2011 6:23 am    Post subject: Reply with quote

Working on a similar project where the goal is to introduce better controls for changes in non-prod. The message is great "we want more control, but none of the bureaucracy". Ain't it great?
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Thu Nov 10, 2011 8:10 am    Post subject: Reply with quote


Great to hide behind a term that has lost its meaning by becoming a pejorative.

One of the dictionary definitions of a bureau is "an agency for the co-ordination of related activities". Just consider that your procedures are such an agency.
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003

Forums ©


Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.