What are the best practices for transferring knowledge?

Question

If you find yourself in a situation where the main developer of the project you are working on decides to leave.

He has all the knowledge, was in the project from the very beginning. If you are lucky, you can get something like two months of his stay in the project, if not, it can only be a notice of withdrawal within a month.

What are the best practices for knowledge leakage, transmission?

What has been helpful to you in the past? Pairing, presentations, documentation?

Answer 1

, . , 2 .

, . , , .

, 2 . , , , . , , .

2 3 . . , .

Answer 2

, , , , .

, . , .

Answer 3

. , . , , , ,

Answer 4

, , - . , - , //.

, - , , , - , , . , , , , , .

( FWIW , UML - - , , )

Answer 5

, , /, . -, , . , , - ..

, . , :) , , , 1-2 , . , .

, , , .

.

Answer 6

, , .

, - - , . , . , , . , .

, , . , , .

Answer 7

Like the static documentation of what the project is currently about, I also record which demonstrations / experiments were performed and which decisions were made. The project trajectory is important in terms of knowing what has already been tried and failed, and which parts are in technical debt and why.