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


Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more