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

Current Membership

Latest: D61Y
New Today: 41
New Yesterday: 79
Overall: 144676

People Online:
Visitors: 53
Members: 2
Total: 55 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - Same or separate?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Same or separate?

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


Joined: Dec 02, 2009
Posts: 9

PostPosted: Fri Jan 15, 2010 9:28 am    Post subject: Same or separate? Reply with quote

Hi all,

Seeking some advise on what people have done in the past for Singular Major Projects with regards to CAB.

In the next few months my company will be running a complete infratructure upgrade for the client.
From basic pre project meetings and my knowledge of the current environment, i would suggest 600+ RFC over the life of this project.

Would you run a seperate project CAB for this one project? (CM has been costed) keep it in all in the same current CAB since everyone needed is already there? or something complete different that i havent thought of Shocked

look forward to the brutal comments Wink
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Fri Jan 15, 2010 8:00 pm    Post subject: Reply with quote

S_B,

the changes will be made to the working environment and therefore must be controlled alongside all other changes and activities there. There can be only one schedule of changes to any environment. Who is on the CAB for any specific change should be determined by the areas of impact, expertise authority and responsibility required in the change.

So, if you mean that the membership of the CAB may differ from the normal one, then, perhaps, but on a case by case basis.

But if you propose a separate management structure for changes required by the project, then that would be, at the least, extremely dangerous.

And if the project team is thinking of fast-tracking or bulldozing, I would not recommend that. A project, however large and important, must adhere to all relevant management processes and not supplant, short-cut or undermine them.
_________________
"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
viv121
Senior Itiler


Joined: Dec 15, 2007
Posts: 113

PostPosted: Sat Jan 16, 2010 3:18 am    Post subject: Same or separate? Reply with quote

S_B,

You asked for brutal comments. I guess you are being brutal on other change requestors with 600+ RFCs lined up to be produced in CABs. You can probably influence the management to call up special CABs or influence them to get an exception letter for yourself to have a separate CAB. All this when the management you are referring to are also the stake-holders of the production environment and business represntatives. Its important that they use the same scale which is used by the normal CAB to assess the impact and risk.

Lastly, am assuming that you are doing phase-wise roll-outs. Big bang will boomerang. Try identifying business users who can agree to be pilot users and report all known issues to a pilot helpdesk. The information collected by the pilot helpdesk can be effective in post production support. The reported issues could act as knowledge documents from the first line to the third line of support.If the pieces of project are piloted, then there would be less chances of changes going haywire after implemenation.

Regards-Viv
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 http://www.nukecops.com

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.