In Conexiam’s Navigate, a set of standardized classes of stakeholders, concerns, and associated viewpoints are maintained for each architecture purpose. This follows the advice of aligning the EA Team with the questions that are expected to be answered.
This standard list of common stakeholders, concerns, and their alignment are provided as a starting point for an EA Team that needs to address common questions.
The table shows the relationships between the stakeholder classes and concerns for a single architecture purpose.
Common Stakeholder Classes
- Senior Leaders are those with responsibility for management and oversight. This responsibility includes approving and realigning strategic initiatives, tracking a portfolio of projects, ensuring transformative benefits are realized, and meeting operational business goals.
- Program/Portfolio Managers are those with responsibility for management and oversight of strategic initiatives. This responsibility includes approving and realigning projects, tracking project progress, and ensuring project benefits are realized.
- Business Requirements Owners are those responsible for identifying and expressing business requirements. Typically, these stakeholders are responsible for some aspect of business operation.
- Implementers are those responsible for developing, integrating, and deploying the solution.
- Risk Owners are those interested in risk.
- Business Partners are those who are engaged to provide services sustaining a customer value proposition. Note: The architecture may not be provided to business partners, but must be evaluated from their perspective.
- Customers are those who consume products and services. Note: The architecture may not be provided to members, but must be evaluated from their perspective.
Common Concern Classes
- Agility: what is the ability of the architecture to adapt to future unanticipated change?
- Efficiency: how does some aspect of the architecture contribute to efficiency of operations?
- Differentiation: how does some aspect of the architecture address enable differentiation?
- Value: what is the value of the architecture?
- Value Proposition: how does some aspect of the architecture address a value proposition?
- Change Cost: what is the impact of a change to the architecture in terms of cost of change?
- Change Impact: what is the impact, or scope, of a change to the architecture?
- Alignment: to what extent is the architecture aligned with priorities?
- Feasibility: what is the probability the architecture will be realized and sustained?
- Dependability: how will the architecture consistently deliver value and operate safely?
- Control: how will we protect assets in the architecture?
- Specification: what needs to be built?
- Security: will the architecture consistently address the risks and opportunities embedded in operations?
- Confidence: what confidence can be placed in the target?
- Customer Intimacy: is the Enterprise delivering products and services the customers want? What is the confidence that the new product or service will be liked by them?
- Scalability: Can the architecture and the Enterprise handle the range of demands and growth cycles?
- Business Continuity: Does the architecture provide the appropriate level of continuity needs relative to the Enterprise’s needs?