1. Knowledge Transfer Process for Developers From Harsha Amin.

2. Current Knowledge Transfer Process Meetings & Calls with the exPrototyper. Team members who are continuing guide fresher. Documents available for developers are Prototype and SSAD. If you are New to the Team you are astonished like him for the half of the Semester. I am not new still I was in his place initially.

3. Sites referred while coding by all the builders in 577a&b should be stored. Prototyper should make a document regarding the Language used. References to materials and online sites that the coder has used himself. IIVer’s should also verify prototype code if standards are followed, comments are there,…and all coding aspects. Builders should make a wiki page.

4. I would suggest a tool to be implemented which stores the search query string and the sites visited by all team members and stored in common repository, so that its referred by team. Searching takes up lot of time which can be saved by this tool. Store A to Z during the process of coding into a document for reference.

5. The code should also be submitted as one of the submission documents. Bugs in code should be reported by bugzilla so that coders rectify it early. Code Review should be conducted twice and not only at the end. This would make the developer correct the errors in early stages.

6. Bug free code according to standards Satisfied developer Documented Knowledge Transfer Standard Coding Team Repository Satisfied Client