Stakeholder Management is critical to successfully initiating and maintaining an architectural program. Architects will need to engage with a wide range of stakeholders from senior executives down to implementation staff. The engagements will often require political sensitivity, diplomacy and flexibility to ensure the stakeholders' needs and concerns are dealt with appropriately. Providing relevant and tailored views of the architectures will be critical to ensuring that the stakeholders are kept informed and that they spend the time needed to understand the impact the architectures will have on their domain. Having a comprehensive communication plan is critical to ensure that the stakeholders receive the information they require and to maintain an interest and input into the architectures.
Enterprise Architect has a wide range of facilities and tools that can assist with the stakeholder management. This includes the ability to model the individual and groups of stakeholders, to classify them in a taxonomy and to show the extent of their influence by using a series of nested Boundary elements. There is a wide range of diagrams, matrices and lists that will be relevant to certain stakeholders, including 'List' presented in the Specification Manager, Component diagrams describing Applications, and Class diagrams used to present the information architectures, principles and a range of other ideas. The Calendar and Model Mail are useful tools for keeping stakeholders informed about things of interest and important events in the architecture program.
This section lists the main tools available in Enterprise Architect that can be used to perform Stakeholder Management. There is also a wide range of additional tools that a modeler might find suitable when applying the technique in a particular context. The complete list of tools is available from the topics Meet the Enterprise Architecture Tools and Additional Enterprise Architecture Tools.
The Class diagram can be used to create visual representations of the stakeholders including how they are related to each other. An alternate image can be used to make the diagrams more appealing and to visually represent stakeholder groups. They are also useful for presenting parts of the information architecture such as conceptual and logical models. Principles can be displayed and communicated using a class diagram and their relationships to other parts of the model can be demonstrated.
Learn More: Class Diagram
The Component Diagram can be used to show the relationship between stakeholders and parts of the solution that affect them or that they have an interest in or a concern about. The diagram could explain the reason for their interest which helps Analysts and others to notify the stakeholders when important milestones are reached. They can also be useful to show any number of Application or Interfaces in the context of other parts of the architectures.
Learn More: Component Diagram
The Boundary element can be used to group stakeholders visually. This is a powerful mechanism and can be used to create an onion diagram showing the relative influence that groups of stakeholders have on an initiative.
Learn More: Boundary
Many of the stakeholders will be managers or non technical staff who will benefit from viewing diagrams with graphics. Images from the standard Image Library could be used or an organization is free to create their own graphics to represent individual stakeholders or stakeholder groups.
Learn More: Element Appearance
The Image Library is a global store of images in the repository that can be applied to any number of diagram elements. The images can be in a variety of formats and when used to change the appearance of an element they create a compelling diagram that is often more appealing to managers or non-technical audiences. Where possible it is recommended to store a vector based image so that it can be effectively scaled in a diagram. The images can also be used when defining the metafile for a stereotype.
Learn More: Image Manager
Model Mail can be used to communicate with stakeholders, to alert them of important events that are relevant to them and advise them of outcomes, decisions and required actions. Links to model elements, diagrams, matrices, Team Reviews and a variety of other items can be added to a mail message.
Learn More: Model Mail
Organizational Chart Diagram
An Organization Chart Diagram is a useful tool to show the structural and organizational relationship between stakeholders and to understand reporting lines in an enterprise or department.
Learn More: Organizational Chart Diagram
A Relationship Matrix can be used to present a number of views of the stakeholders. The matrix is a spreadsheet like view that is often more appealing to many managers and non-technical audiences. Any number of matrices can be created that relate stakeholders to other models elements including other stakeholders.
Learn More: Relationship Matrix
The Requirements diagram is useful for showing the relationship between stakeholders and their Requirements and allowing communication about the way the Requirements are managed. Diagrams that display traces between the Requirement and the solution Components will also be important for ensuring that the stakeholders understand how their problems or opportunities are being solved.
Learn More: Requirements Diagram
The Specification Manager is a useful tool for working with lists inside Enterprise Architect which makes it the perfect tool for working with lists of stakeholders and personas.
Learn More: Specification Manager
The Calendar is a useful tool for communicating information about project milestones and events which will facilitate good communication with the stakeholders. This includes providing hyper-linked references to the parts of the model including matrices and diagrams that are of interest to them.
Learn More: Calendar