Skip to main content

Certified Enterprise Architect Professional (CEAP) : Module 18 : Managing Stakeholders

Stakeholders:

Stakeholders are people who have key roles in, or concerns about, the system e.g. users, developers etc. Stakeholders can be individuals, teams, organisations, etc.

Concerns:

  • A general type of interest (e.g. availability, usability) that is significant to one or more stakeholders in the system, and controls the acceptability of the system to those stakeholders.
  • A concern may be addressed from several viewpoints.
  • A viewpoint may address several concerns.
Role of enterprise architect in Managing Stakeholders:

An enterprise architect plays a crucial role in managing stakeholders by actively engaging with various groups within an organization, understanding their needs and concerns, and ensuring that the designed IT architecture aligns with the business goals of all stakeholders, effectively communicating complex technical details to diverse audiences to gain buy-in and support for the overall enterprise architecture strategy. 

Key aspects of an enterprise architect's stakeholder management:
  1. Identifying and analyzing stakeholders
  2. Communication and collaboration
  3. Relationship building
  4. Managing expectations
  5. Negotiation and conflict resolution
  6. Tailored communication strategies
  7. Stakeholder engagement throughout the lifecycle
Tools and techniques used by enterprise architects for stakeholder management:
  • Stakeholder analysis
  • Architecture documentation
  • Visualization tools


Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .