Quote:
Originally Posted by Jamz
You may also want to try some XP/Paired programming if you have newer devs. It may seem like a waist of resources to have 2 developers working on the same issues but the amount of context sharing and knowledge transfer you get is better than having a new dev "figure things out" on his own for a whole sprint.
|
As a project manager I've tried pair programming to bring new/junior devs up to speed and it has always been a dismal failure.
Finding two coders who think/work the same way is just not realistic. The senior also likely knows the system and knows exactly how to fix the problem/add the feature and finds it frustrating to explain everything. The senior dev doesn't get work he should be doing done and the junior doesn't really do anything and likely doesn't learn very much since he didn't do all the tracing of code and exploring that would have been required for him to do the task himself.