08-03-2006 3:50 AM
Dear Gurus,
When rolling off, a developer may be asked to hand over knowledge of codes developed to the next person.
Is there no way to hide knowledge during such a process given that codes can be read by any developer?
I like to know how to handover without actually handing over knowlege as much as possible.
Pls share with me this skill.
Thanks,
t.d
08-03-2006 3:53 AM
08-05-2006 3:41 PM
Your employer has paid you for that knowledge. So if they ask you to pass it on to the next person, that is what you must do.
08-05-2006 4:13 PM
> Your employer has paid you for that knowledge. So if
> they ask you to pass it on to the next person, that
> is what you must do.
I agree totally. When we roll-off of a project and have "knowledge transfer", we go through a review process for each program. The developer meets with the client team lead and client developer. We do a code review and go over the functional and technical specification documents.
Some client contracts carry legal requirements. I have seen development objects listed as "type 1", "type 2", or "type 3". In some cases, the code is owned by the client and you cannot legally re-use it at any other site. Other cases declare the source code as "shared". You can re-use it at a new project. The third case may declare it is owned by the consulting firm or implementation partner. The client cannot share it with outside sources.