ABOUT SES
IT SERVICES
SES ADVANTAGE
INDUSTRY EXPERTISE
CAREER OPPORTUNITIES
CONTACT US
 

Quality Assurance Program
Collaborative InSourcing
Off-site Development
Pricing Options
Screening Processes
Resource Development Program
Knowledge Transfer Plans

Knowledge Transfer Plans
One of the key components of our unique approach is to ensure your company’s self-sufficiency down the road.  To accomplish this goal, SES recommends developing a formal “Knowledge Transfer Plan” at the beginning of every client engagement.

The purpose of an SES Knowledge Transfer Plan is two fold: First, to bring SES' Systems Engineers up to speed on your business and technical environment and second, to ensure that your employees are capable of supporting their systems at a certain point in time without needing further assistance from SES.  Because your employees will be working together with SES engineers on the project team, this transition will be a natural progression.  In addition, SES will support a training and mentoring plan to help pass needed skills to your personnel over an agreed upon schedule.  Recipients of knowledge transfer should consist of personnel from different areas of the company, not just those on the development team.  The exact approach to be utilized depends on the target audience.


SAMPLE KNOWLEDGE TRANSFER ACTIVITIES:

  • Code reviews


  • Participation in construction of documentation


  • Pair programming on certain tasks (an Extreme Programming concept)


  • Project Presentations on topics of overall importance


  • Project-Specific Training (internally developed, as needed and requested)


  • Certification Training programs (mandatory or voluntary participation)


  • Brown bag sessions (i.e. during lunch breaks)


All SES Knowledge Transfer Plans include a scheduled de-staffing plan of SES consultants that provides a smooth transition to your company’s system support team.  The advantage of a formal SES Knowledge Transfer Plan is that your company knows from the beginning that they will be self sufficient at project completion.  Now you really do have a better way…