Bit of an odd one this, hopefully someone can give some tips..

Ive been given the "awesome":rolleyes: objective of getting some kind of framework together for service and application handover documentation. as it is there is nothing in place and ISD/ITI just throw stuff at us (operational support) without supporting docs.

I have no idea where to start on this.. ive written some random stuff down but its by no means exhaustive..

Is there any kind of "official" way to do system/application handovers? ie with regards to documentation and support?

what happens in your companies when developers bring out new stuff and expect you to support it?

any help/pointers would be appreciated, all this work ive been given are leading me towards more of a project managment role, but im new at all this so its all a bit daunting!

Thanx in advance

Col G

If you check out the bcs websites under ITIL, you should find a massive amount of info about this, with templates etc. I'll dig about and see whether its for bcs members or not.

If you check out the bcs websites under ITIL, you should find a massive amount of info about this, with templates etc. I'll dig about and see whether its for bcs members or not.

Interesting

We have "skills transfers" where the developers give us presentations on all the wonderful features they're put in and how they (should!) work. We've also managed to persuade them that doing some written design when they do them is also pretty useful and we get access to this too.

Chris

If you check out the bcs websites under ITIL, you should find a massive amount of info about this, with templates etc. I'll dig about and see whether its for bcs members or not.

Cheers, was looking at that BCS site and it seems like a paid membership thing

Yeah unfortunatly it is. I'll see what I can scavange

What usually happens is I get a fault call passed to me , and I have no idea what the user is talking about , as it's something I've not been shown before or even beenmade aware of it's existance.

I assume you want to know what *should* happen instead?

What usually happens is I get a fault call passed to me , and I have no idea what the user is talking about , as it's something I've not been shown before or even beenmade aware of it's existance.

I assume you want to know what *should* happen instead?

yes, ive got to try and produce a "perfect world" framework

pm'd you Colin

pm'd you Colin

Coolio.. cheers

Aye ITIL or there is some stuff within BS7799 / ISO27000

Aye ITIL or there is some stuff within BS7799 / ISO27000

I shall look into ITIL.. presumably it comes under release management part of it.

(i recently passed my ITIL foundation course lol)