2 ms·
Do you mean people not handing down tribal knowledge? Or preventing something from becoming tribal knowledge to begin with? If the goal is to avoid something
by LinuxBender 5y ago
Do you mean people not handing down tribal knowledge? Or preventing something from becoming tribal knowledge to begin with?
If the goal is to avoid something becoming tribal knowledge, then don't consider a project complete until it has been documented and a completely different team has deployed and supported the project without any need to talk to the engineers/architects/developers that created the project. There will always be feedback loops to improve a project, but if a completely unrelated team can't deploy and support something, then you have tribal knowledge that has not been communicated in documentation, including self documenting code and/or videos. There is much more to this of course and hopefully others here will add more tips.
- tra3 5y agoThis is like automated testing. Perceived value is high -- so why is it so rare?
- richardknop 5y agoVery time consuming so probably lot of companies will skip on this to deliver features faster. Having robust documentation that contains all the knowledge so a completely new team without any project knowledge can easily deploy/support the project can be a big task, especially for large projects. Even with really good documentation, there will always be required some handover and initial training from the maker team in my experience, it is almost impossible to avoid this. I guess during sprint planning, if this requirement is being included and the estimates from developers start doubling suddenly the product team might compromise in order to move faster.