OOA&D will change team
Using OOA&D principles will change your team, sometimes in ways team members won't be comfortable with at first. It may be hard for the best programmer on your team to defer to a junior member who happens to be a real whiz at class discovery.

One good take on team roles comes from Object Solutions: Managing the Object-Oriented Project, by Grady Booch (Addison-Wesley). Booch says that except for very large projects, there should be exactly one architect for a system. The architect is both the keeper of the vision, and the knight who defends that vision against the inevitable entropy of the system (an elegant design degenerating into chaos as functionality is added). The architect needs to be familiar with the language(s) used in the system and should have the best domain knowledge and strategic understanding.

Booch also recommends assigning "abstractionists." An abstractionist needs some of the same skills as the architect, but without necessarily the same breadth of experience. Abstractionists tend to be better programmers and are the subset of the engineers/programmers on the project who are most skilled at discovering the classes. —LJJ