From my book:
13.6 Different roles of an enterprise architect
Below is a list of the roles which should be effectively fulfilled by any enterprise architect in order to use EA as a tool for improving an enterprise.
- Scribe who keeps up to date the documentation about EA artefacts and the relationships between them. This is the traditional role of an enterprise architect.
- Scout who brings new technologies into the enterprise.
- Salesman who finds good arguments for investments in not-so-obvious improvements.
- Superman who is usually asked to provide a quick rescue for a rotten IT project, often by completing during the weekend work that should have been done over many man-months!
- Sociologist who has to understand the concerns and fears of everyone in the enterprise.
- Servant who is at the service of all others in the enterprise.
- Scientist who uses scientifically proven methods in his/her work.
- Student who is ready to learn quickly new technologies, new tools and new business domains.
- Shepherd who can guide others.
- Secretary “de luxe” who helps others to do some work (although this may be considered as a rather low qualification, it is nonetheless important to achieve the common goal).
- Skipper who can lead complex projects.