ServiceOrientedArchitect

• The role of "architect" provides a service to a team, rather than directing them. This is somewhat less true of team leaders, and somewhat less true again of project managers. But in all cases becomes more true as the team size increases. -- KeithB

I think I have to disagree to some extent. I don't think your statement is any less true of team leads or project managers. I think that both project managers and team leaders should view themselves as providing a service to their team/project. After all, the team members are usually the units of production, managers facilitate. The managers should be focussed on ensuring the whole team (and it's members) is working at maximum effiency (including human issues). Therefore, the service they provide is that of ensuring the smooth and healthy running of the team/project etc etc. When observing projects where the development team/manager haven't gelled, it is often because the manager does not see themselves as a service. Extending this further, I think the best teams have members who see their relationships as composed partly of service to the others - mutual dependency (like any good community). It is the recognition that everyone depends on everyone else that assists in keeping a team running well.

BTW: Why do you think this service orientated approach becomes more obvious as team size grows? My experience leas me to believe that it's pretty invariant on team size. A lack of this service viewpoint makes small teams dysfunctional as well. Even in a 2 team, mentor+student setup, there is still mutual dependency and the mentor should still consider they are providing a service. -- AndySchneider?