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.
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.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
The Itil Community Forum: Forums
ITIL :: View topic - How do I change a non-existent service?
Joined: Mar 31, 2008 Posts: 109 Location: North West England
Posted: Wed May 07, 2008 11:16 pm Post subject: How do I change a non-existent service?
Hello ITIL Experts
Here is an interesting conundrum I would like your advice on.
My employers public internet website has been designed and is hosted by a third party and we just update the content as required. The website is therefore not listed as an ITIL Service.
My employer wants to perform a minor restructure of the website and therefore someone has raised an RFC to cover the work. My question is:
As the Change Manager, how should I handle an RFC against a service we don't recognise? Should I reject it, allowing the work to go ahead anyway? Should I handle it as a minor change, just so it's logged? Or should I do something else?
Thanks in advance _________________ Mick Smith
Change, Configuration and Release Manager
Joined: Mar 31, 2008 Posts: 109 Location: North West England
Posted: Thu May 08, 2008 12:05 am Post subject:
Thanks for the reply but I wasn't obviously clear enough.
Ignoring whether it should be an RFC or not, I'd like to know how to handle a submitted RFC when I do not formally recognise the service it is related to? It is ok to just reject it?
Although I am undecided whether my example should have been rasied as an RFC in the first place, the requestor thought that changing the structure of a website (not the content) was worthy of an RFC. It therefore needs to be handle (if only briefly) by change management. _________________ Mick Smith
Change, Configuration and Release Manager
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Thu May 08, 2008 12:07 am Post subject:
Hi,
structural change isn't exactly just content change. Where does the responsibility lie? does your third party supplier undertake design maintenance or do you? Will structural changes undermine the maintenance contract?
There is a change to be managed. The question is whether it is your management that is required or your service provider's. Probably this had not been thought through when the service was commissioned.
Once you can answer these questions you can determine where responsibility lies and, therefore, whether the structure of the website should be in your CMDB or not. _________________ "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
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Thu May 08, 2008 12:13 am Post subject:
Hi again,
my reply overlapped.
mnsmith wrote:
Thanks for the reply but I wasn't obviously clear enough.
Ignoring whether it should be an RFC or not, I'd like to know how to handle a submitted RFC when I do not formally recognise the service it is related to? It is ok to just reject it?
Although I am undecided whether my example should have been rasied as an RFC in the first place, the requestor thought that changing the structure of a website (not the content) was worthy of an RFC. It therefore needs to be handle (if only briefly) by change management.
An RFC implies that something your service management is responsible for. However if you are not responsible for it, then you obviously reject the RFC on the grounds that you have not been asked to do anything within the scope of the service.
From the perspective of the Change Management function requesters are lay people. They know they want something, but they don't always no how to achieve it. So sometimes they think it best to raise an RFC when that is inapproprite; you just tell them that (and, of course, help to guide them on how to achieve what they want).
I'm rambling because I'm thinking as I type. _________________ "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
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
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
