hi all, i have been asked to look at different methods of development since we do a lot of agile dev and the trend is since developers are so involved with projects when they leave the knowledge walks out the door with them. Anyone know how this situation can be improved ??
Yes. Make it so that they do want to stay. Seriously.
Well, there are some ways to spread knowledge in the team, with pair programming probably being the most effective one by far.
But there always will still be a lot of tacit knowledge, no matter what you do, so the most important strategy should be to not loose developers.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Do documents really keep knowledge? No - they get stale.
There are ways to mitigate the damage and keep the knowledge:
1 - Automated test suite - especially around requirements. 2 - Pair programming 3 - Using workshops during requirements and design to spread the knowledge 4 - Evocative documents instead of representational documents.
Amr Elssamadisy<br /><a href="http://www.amazon.com/Agile-Adoption-Patterns-Roadmap-Organizational/dp/0321514521/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1220909336&sr=8-1" target="_blank" rel="nofollow">Agile Adoption Patterns</a>
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com