Knowledge Transfer (KT) has become an important phase for different reasons such as ‘Outsourcing’, ‘Remote Workplaces’ and ‘High rate of attrition’ etc. Often KT is viewed as time-consuming costly effort and eventually could become a bottleneck for an organization hindering its future plans.
Agile methodologies like Scrum and Xtreme Programming (XP) can always be advantageous not just because of the various beautiful features they offer but also due to the flexibility and control they empower the users with. With minor tweaks to the process, KT can easily be incorporated into these. The whole idea of these agile methodologies is breaking a big task into multiple smaller tasks. Since the actual tasks are so small, both business functionality and technical aspects can easily be understood and documented.
One of the beautiful features of XP is Pair Programming. It’s a misconception that two equal heads (should) form a pair. A team consisting Subject Matter Experts (SME) and new resources coming on board can easily embrace this and can be divided into different pairs of SME-Newbie. So the whole idea of KT is built-in with XP
With right planning and good practices which come with Agile methodologies, KT is often a boon than a burden. The importance baseline is that all the knowledge transferred should be captured and gained. There are several best practices and tools which help in this.