Retrain your code czar

Many software organizations have two classes of technical staff: normal employees and royalty. The royalty-those kings, queens, and czars of software development-initiate central controlling project roles. They see a dire project need and act on it, though no one asked them to. Royalty believe they provide unique project and product skills for the organization. They may, but, in my experience, their controlling actions prevent the project and the team from developing products and cohesive processes. When one team member takes on the royalty role, it prevents the rest of the group from learning what she already knows. The team becomes fragmented and can't work together; the problems that created the royalty become even worse. Royalty delay projects because they interrupt the normal development loop of creating the product, testing it, fixing it, integrating it, and getting feedback. The royalty must stay in their chosen role, because the participants eventually come to believe that the project cannot make any progress without them.