Knowledge Management enables organizations to readily share both their explicit recorded knowledge and the elusive tacit or intellectual knowledge. It is always a challenge to document and share across all tiers of the organization the intellectual capital which is generally elusive and collectively held in the brains and experiences of its key employees. A knowledge-aware organization, which has realized the value of the wealth of knowledge & created a platform to share it seamlessly, is able to react quickly to external demands, leverage internal resources intelligently and anticipate external market directions and course changes. It is so very true for the success of your business and any outsourcing relationship you may decide to get into, today or tomorrow - the potential rewards are significant.

C3IT believes that knowledge management strategy is an indicator of a “Learning Organization”. Hence, in our business, even if the clients probably have not fully thought through all the aspects of developing a Knowledge Strategy - its implications if they do, and its implications if they don't - C3IT takes upon itself the role of a facilitator and enabler to secure the intellectual property of its clients.

C3IT has taken the initiative and established a Software Engineering Process Office (SEPO) that maintains the corporate process asset library. It contains a comprehensive set of software engineering assets such as tailorable processes, plans, templates, and guidelines for areas such as requirements management, configuration management, quality assurance, training, reviews, testing, estimation, and most importantly, project management including planning, risk management, tracking and oversight.

An engineering and project management library is also available to C3IT employees who can review and/or checkout a variety of systems and software engineering books, audio and videotapes, and a multitude of documents.

The Software Process Improvement group meets periodically to provide information on engineering and project management topics and process improvement.

SEPO works with the Process Improvement group to implement engineering and project management process improvement by identifying project management, and systems and software engineering needs, providing Center-wide engineering and project management best practices, facilitating the generation of process improvement plans, and project-specific process definitions and documentation requirements in concert with organization best practices.

SEPO conducts variety of training and workshops on project management, software engineering management, process improvement, peer reviews, and team training.

SEPO maintains contacts and memberships with external engineering and project management entities by attending conferences and meetings and participating in both Government and industry working groups like NASSCOM, Electronic & Software Export Promotion Council, Nokia Forum, Sony Ericsson, and Qualcomm

C3IT uses the following process for knowledge sharing:

Knowledge Transfer

The knowledge transfer, first from the client end to C3IT offshore team, and thereafter back to the clients for the developed software is an integral part of C3IT’s knowledge management & delivery process. While the knowledge transfer of your business, processes, functions, organization and its operations to C3IT offshore team is very important for our consultants to gain insight into the business objective of developing a new software, C3IT is equally sensitive to this fact that as the owner of your software, you would like to retain the knowledge of the new system we develop for you as also reduce your dependency on us in order to meet your requirements on an on-going basis or in future, as the case maybe. After all, you need to be in complete control of your software and the knowledge that resides therein.

C3IT carries out the two-way knowledge transfer using the following process:

• Briefing from the existing team/stake holders regarding the existing system.
• Walk through business requirements
• Walk through the existing system
• Study functional documentation
• Walk through technical documentation
• Study user documentation
• Study existing implementation
• Work with the existing team as a part of the team

Following medium(s) are used to effectively conduct the knowledge sharing sessions: