• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Reply to: Knowledge Transfer

Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Knowledge Transfer"

Collapse

  • darmstadt
    replied
    I had to do a transfer in my last gig for one product which consisted of handing over everything I had done in the last 2 years (documentation, test plans, programs and scripts, etc.) to someone who had never used the product. I didn't feel it was my remit to show him how the product worked although I did give him a basic introduction in it. Luckily I had set up the systems so that when a new release came out all he had to do was follow the documentation and the rest was pretty much automated. He would only hit problems in debugging as he wouldn't know where to look or what to look for. For another product I did no skills transfer but made sure that everything was documented and available.

    Everytime I've left a contract there has been some form of skills transfer and I tend to spend my last week setting up a system where people can easily find the information and then on the last day tell the customer that he is free to contact me at any time. This has worked to my advantage with them contacting me for quick, short and dirty projects to help them out.

    Leave a comment:


  • Sockpuppet
    replied
    I had to do some handover when I left last client co.

    I taught them to do what I had set up. Run what I had produced and adapt it for the coming year.

    I didn't train them in solutions design or mathematical network modelling as although they are needed to do the job not what I was paid to do.

    I handed over what I had done. if they want more doing they know where to find me.

    If they had asked me to make one of their permie staff me I would have but at a sensible rate.

    Leave a comment:


  • MrMark
    replied
    Originally posted by BlasterBates View Post
    You can do what ever you like. You can sit on a stool and hoot like an owl all day, if you want to. You just need to ensure that you're doing something of sufficient use so that the company don't throw you out.
    Damn, I knew there was a reason why I'm stuck on the bench...

    Leave a comment:


  • AnthonyQuinn
    replied
    Thanks a Lot

    Thanks a ton for your useful comments. They are very helpful.

    Leave a comment:


  • BlasterBates
    replied
    You can do what ever you like. You can sit on a stool and hoot like an owl all day, if you want to. You just need to ensure that you're doing something of sufficient use so that the company don't throw you out.

    Leave a comment:


  • Not So Wise
    replied
    It's not really controversial in any shape or form

    Look at it this way, say you were a .NET developer and worked at a client for 2 years and they asked you to do Knowledge transfer.

    This would consist of doing and handing over documentation of all system's applications under your remit (and after two years you should have a lot)
    Making sure recipient knew who to talk to in situation X
    Some training in those systems undocumented quirks (always some)

    It would NOT consist in training them in .NET

    If they have appointed recipient of the transfer that did not know .NET (and thus all the other stuff being useless to them) you would just inform the client of such, hand over the documentation and leave it at that, their problem not yours

    Knowledge transfer is transfer of knowledge of clients process's and systems it does not consist of skill training, that costs extra…a lot extra

    Leave a comment:


  • MPwannadecentincome
    replied
    if they need to know SAP they should go on a SAP course. Alternatively offer to run a customised SAP course for your client at double your normal rate.

    Leave a comment:


  • Ravello
    replied
    Personally I'd say the answer is no, you don't. My assumption for this statement is that you didn't pick up the product skills onsite, and therefore this is not 'client knowledge', but rather your skills.

    As a PM I don't expect to transition Prince2 skills to anyone I'm handing over a Project to!

    Leave a comment:


  • AnthonyQuinn
    started a topic Knowledge Transfer

    Knowledge Transfer

    Dear All
    My client is asking me to conduct knowledge transfer sessions to permanent staff in an attempt to ease me out. As a professional, I understand their constraints. I cannot and will not resist this and will conduct the KT in the best manner possible.

    However, my question is, as follows

    I am a business analyst. I can transition my documents, ways of working etc, bring my replacements upto speed with the project etc. But, if I possess some in depth product skills, say SAP HR or Peoplesoft, do i need to train / upskill them on this?

    I know this is controversial. I just want to do my job properly without actually going beyond my call of duty to expedite my removal.

Working...
X