This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm not sure where to post this. Anyway I'm writing to find out if anyone has any resources/urls describing how to manage a team with multiple senior developers. Basically the team recently hired a new senior developer. Since there's already one "chief"/"architect" on the team; I need to know how best to structure the team so that the two chiefs can co-exist together without tearing at each other's throats. And yes, we currently run the team using a homebrew variant of XP.
By getting rid of official titles and explicitly stating that there's no chief this or that in the team and that everyone should turn to whoever has the knowledge or experience on a given topic for help (implying that this may or may not be the most senior person in the team...).
Kent Beck once started to write a book about leadership in XP (and other self-organizing) teams. The script never got big enough to be worth while being printed, but it might still be an interesting read.
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