复杂系统的复杂不仅在与架构开发流程本身,还与是否获得大范围涉众的一致同意有关,涉众管理的好不能肯定企业架构一定做得好,但是涉众管理做得不好,企业架构肯定做不好。对于管理类型项目来说,客户的满意度有时就能体现出我们和客户一开始交流得够不够。在A阶段(架构愿景)中我们需要进行涉众管理,交付类似下图的Stakeholder Map Matrix。本篇介绍一下涉众管理。

好处

  1. 标识重要的涉众,能在早期更好的框定架构需求和范围
  2. 通过重要涉众的支持,可以获取更多的资源
  3. 早期频繁的和涉众沟通,可以确保更完整的理解架构流程

管理流程

  1. 获取涉众列表

    • 谁从项目中收益或遭受损失?
    • 谁控制项目?
    • 谁来设计系统?
    • 谁作出决策?
    • 谁获得IT系统并决定是否购买?
    • 谁控制资源?
    • 谁有项目要求的专业技能?
    • 谁对项目有影响力?
    • 问发起人或客户
    • 检查组织机构
    • 比较类似项目组

  2. 认识涉众的态度
    • 这个人是否准备好了从当前现状改变到目标架构上?如故事,准备怎么改变?
    • 这个人是否有能力作为一个企业架构发动人和推动者?如果是,他有什么能力?
    • 如何参与到企业架构活动中?只是感兴趣了解而已,还是需要详细了解?
    • 对企业架构的开发是否有合约性的承诺?

    涉众分组

    涉众

    推动力

    当前清楚改变

    需要清楚改变

    当前责任义务

    需要责任义务

    需要支持

    CIO

    张三

    CFO

    李四

  3. 知道关键涉众: Power/Interest
    • A 不关注他
    • B 让他知道
    • C 使他满意
    • D 与他协作

  4. 裁剪涉众相关交付视图(ViewPoint)

  不同项目中自行进行裁剪,在TOGAF文档中举了一个裁剪示例

涉众

参与

分类

相关视图

CxO
(Corporate Functions);
e.g., CEO, CFO, CIO, COO

This stakeholder group is interested in the high-level drivers, goals, and objectives of the organization, and howthese are translated into an effective process and IT architecture to advance the business.

KEEP SATISFIED

Business Footprint

Goal/Objective/ Service Model

Organization Chart

Program Management Office
(Corporate Functions);
e.g., Project Portfolio Managers

This stakeholder group is interested in prioritizing, funding, and aligning change activity. An understanding ofproject content and technical dependencies between projects adds a further dimension of richness to portfolio managementdecision-making.

KEEP SATISFIED

Roadmaps

Business Footprint

Application Communication

Functional Decomposition

Procurement
(Corporate Functions);
e.g., Acquirers

Major concerns for these stakeholders are understandingwhat building blocks of the architecture can be bought, andwhat constraints (or rules) exist that are relevant to the purchase.The acquirer will shop with multiple vendors looking for thebest cost solution while adhering to the constraints (or rules) appliedby the architecture, such as standards. The key concern isto make purchasing decisions that fit the architecture, and thereby toreduce the risk of added costs arising from non-compliantcomponents.

KEY PLAYERS

Cost View

Standards View

Human Resources (HR)
(Corporate Functions);
e.g., HR Managers, Training & Development Managers

Key features of the enterprise architecture are the roles and Actors that support the functions, applications, andtechnology of the organization. HR are important stakeholders in ensuring that the correct roles and actors are represented.

KEEP INFORMED

Organization Chart

Organization/Actor/ Location

Enterprise Security
(Corporate Functions);
e.g., Corporate Risk Management, Security Officers, IT Security Managers

Major concerns for this group are understanding how to ensure that the information, data, and systems of theorganization are available to only those that have permission, and how to protect the information, data, and systems fromunauthorized tampering.

KEY PLAYERS

Data Security View

Networked Computing Hardware View

Communications View

QA/Standards Group
(Corporate Functions);
e.g., Data Owners, Process Owners, Technical Standards Bodies

Major concerns for this group are ensuring the consistent governance of the organization's business, data,application, and technology assets.

KEY PLAYERS

Standards

Guidelines

Specifications

Standards View

Application Portfolio

Technology Portfolio

Technology Standards

Executive
(End User Organization);
e.g., Business Unit Directors, Business Unit CxOs, Business Unit Head of IT/Architecture

This stakeholder group is interested in the high-level drivers, goals, and objectives of the organization, and howthese are translated into an effective process and IT architecture to advance the business.

KEEP SATISFIED

Business Footprint

Goal/Objective/ Service Model

Organization Chart

Line Management
(End User Organization);
e.g., Senior Business Managers, Operations Regional Managers, IT Managers

This stakeholder is interested in the top-level functions and processes of the organization, and how the keyapplications of the IT estate support these processes.

KEY PLAYERS

Organization/Actor/ Location

Goal/Objective/ Service Model

Cost View

Application & User Location View

Business Domain Experts
(End User Organization);
e.g., Business Process Experts, Business/Process Analyst, Process Architect, Process Designer, Functional Managers, BusinessAnalyst

This stakeholder is interested in the functional aspects of processes and systems. This can cover the human actorsinvolved in the system, the user processes involved in the system, the functions required to support the processes, and theinformation required to flow in support of the processes.

KEY PLAYERS

Process Flow

Use-case

Service/Information Events

Functional Decomposition

Application - Application Communication View

Data Entity/Business Function Matrix

IT Service Management
(Systems Operations);
e.g., Service Delivery Manager

Major concerns for this group are ensuring that IT services provided to the organization meet the service levelsrequired by that organization to succeed in business.

KEEP INFORMED

Standards View

Enterprise Manageability View

IT Operations - Applications
(System Operations);
e.g., Application Architecture, System & Software Engineers

Major concerns for these stakeholders are: Development Approach, Software Modularity and Re-use, PortabilityMigration, and Interoperability.

KEY PLAYERS

Process - System Realization View

Application - Data View

Application Migration Cost View

Software Engineering View

Platform Decomposition View

Networked Computing - Hardware View

Software Distribution View

Data Entities to Application Systems View

IT Operations - Infrastructure
(System Operations);
e.g., Infrastructure Architect, Wintel support, Mid-range support, Operational DBA, Service Desk

Infrastructure stakeholders are typically concerned with location, modifiability, re-usability, and availability ofall components of the system. In general these stakeholders are concerned with ensuring that the appropriate components aredeveloped and deployed within the system in an optimal manner.

KEY PLAYERS

Platform Decomposition View

Standards View

Enterprise Manageability View

Networked Computing - Hardware View

Processing View

Environments & Locations View

IT Operations - Data/Voice Communications
(System Operations);
e.g., Network Management

Communications engineers are typically concerned with location, modifiability, re-usability, and availability ofcommunications and networking services. In general these stakeholders are concerned with ensuring that the appropriatecommunications and networking services are developed and deployed within the system in an optimal manner.

KEY PLAYERS

Communications View

Executive
(Project Organization);
e.g., Sponsor, Program Manager

This stakeholder group is interested in on-time, on-budget delivery of a change initiative that will realizeexpected benefits for the organization.

KEEP INFORMED

Architecture Requirements

Architecture Principles

Architecture Vision

Functional Decomposition

Application & User Location View

Line Management
(Project Organization);
e.g., Project Manager

This stakeholder group is responsible for operationally achieving on-time, on-budget delivery of a changeinitiative with an agreed scope.

KEEP INFORMED

Application - Application Communication View

Functional Decomposition

Environments & Locations View

Business Process/Functional Expert
(Project Organization);
e.g., Financials FICO Functional Consultant, HR Functional Consultant

This stakeholder group will elaborate the functional requirements of a change initiative based on experience andinteraction with business domain experts in the end-user organization.

KEY PLAYERS

Process Flow

Use-case

Service/Information Events

Functional Decomposition

Application - Application Communication View

Product Specialist
(Project Organization);
e.g., Portal Product Specialist

This stakeholder group is responsible for specifying technology product designs in order to meet projectrequirements and comply with the Architecture Vision of the solution.

In a packages and packaged services environment, product expertise can be used to identify product capabilities that can bereadily leveraged and can provide guidance on strategies for product customization.

KEY PLAYERS

Software Engineering View

Application - Data View

Technical Specialist
(Project Organization);
e.g., Application Architect

This stakeholder group is responsible for specifying technology product designs in order to meet projectrequirements and comply with the Architecture Vision of the solution.

KEY PLAYERS

Software Engineering View

Platform Decomposition View

Process System

Realization View

Application - Data View

Application Migration Cost View

Regulatory Bodies
(Outside Services);
e.g., Financial Regulator, Industry Regulator

The main concerns of this group are that they canreceive the information they need in order to regulate the clientorganization, and that their information requirements are beingunderstood and properly satisfied. They are specifically interestedin reporting processes, and the data and applications used to provideregulatory return information.

KEEP SATISFIED

Business Footprint

Application - Application Communication View

Suppliers
(Outside Services);
e.g., Alliance Partners, Key Suppliers

The main concerns of this group are that the information exchange requirements that they have are met in order thatagreed service contracts with the client organizations can be fulfilled.

KEEP SATISFIED

Business Footprint

Service-Information View

Application - Application Communication View

ArchiMate对ViewPoint的分类

ArchiMate架构语言从视图的目的抽象级别来对ViewPoint进行了如下分类:

Viewpoint Purpose


 

Typical Stakeholders

Purpose

Examples

Designing

architect, software developer, business process designer

navigate, design, support design decisions, compare alternatives

UML diagram, BPMN diagram, flowchart, ER diagram

Deciding

manager, CIO, CEO

decision-making

cross-reference table, landscape map, list, report

Informing

employee, customer, others

explain, convince, obtain commitment

animation, cartoon, process illustration, char

  Viewpoint Abstraction Levels

本文转自 jingen_zhou 51CTO博客,原文链接:http://blog.51cto.com/zhoujg/518615,如需转载请自行联系原作者

企业架构 - 涉众管理(Stakeholder Management)相关推荐

  1. 2010年3月blog汇总:企业架构、团队管理

    3月份主要对企业架构实施进行了一些思考,制定了一些实践指导文档和交付物.后续我将一起持续思考团队和个人管理,本月对"信任"进行了自己的理解. 架构 企业架构 - 业务战略和技术战略 ...

  2. 2010年blog汇总:企业架构、敏捷个人、模型驱动

    去年的今天,我整理了一下2009年的blog(2009年blog汇总:OpenExpressApp.敏捷开发.需求.产品线工程.个人管理软技能 ),今天是2010年的最后一天,又到整理的时间了,今年主 ...

  3. 企业架构(三)——联邦企业架构框架(FEAF)

    文章目录 一.FEAF 1.FEAF的出现 2.FEAF构成 (1)Level 1 (2)Level 2 (3)Level 3--架构模型细化 (4)Level 4--业务架构模型细化(EAP方法) ...

  4. 数贝携手付晓岩老师带你玩转“企业架构”

    D·Talk 资深企业级业务架构师带您轻松玩转架构 重点摘要 1.业务与数据的融合是实践与时代的呼唤 2.企业架构设计如何实现业务与数据融合 3.企业架构的发展方向 前言 数字化时代的到来,构件将成为 ...

  5. 阿里P8架构师20年经验总结成微服务设计企业架构转型之道笔记

    前言 本文涉及两个方面的知识体系,即企业架构知识体系和软件架构知识体系. 企业架构和软件架构虽然都与IT相关,但其知识体系是完全不同的两个领域.一般而言,搞企业架构的人士不明白软件架构的细节和实现,而 ...

  6. 管理软件售前咨询与企业架构

    项目的开始不是在团队成立时开始的,而是在经过售前咨询签订合同那一刻就开始了,对解决方案.管理类软件来说,售前咨询对项目的重要性绝对可以决定一个项目的起点.最近在思考企业架构以及项目经历中的一些问题,考 ...

  7. 优锘科技:企业架构管理平台荣获2021年度创新产品奖

    近日,B.P商业伙伴D大会"2021数字生态年度大赏榜单"正式发布出炉.UINO优锘出品的企业架构管理平台QuickEA荣获"2021年度创新产品奖". 202 ...

  8. 2010年1月blog汇总:个人管理、OEA权限、企业架构

    以后我每个月都在这里做一个小结,顺便把blog也汇总一下.1月份主要增加了OEA的权限支持,在公司研发峰会的做了4次演讲,下旬开始考虑如何做定额项目组的产品架构.与其自己在项目中跌到后总结,不然直接参 ...

  9. 企业业务架构的需求管理与软件开发的供求曲线

    世事唯有变化不变,架构亦如此.企业架构因其庞大的体量,必然蕴含众多引致其变化的因素,即便是一个被仔细切分过的服务也很难保证自己不会变化,何况包罗万象的架构.架构设计并不是为了一味的追求稳定,甚至不是为 ...

最新文章

  1. libcurl库的使用(通过libcurl库下载url图像)
  2. DeepMind提出强化学习新方法,可实现人机合作
  3. 脚本检测到文件特定词后做下一步动作 down restart
  4. Tensorflow之调试(Debug) tf.py_func()
  5. 行为模式之Iterator模式
  6. 2016021701 - 百位名人读书心法01
  7. Java架构师必备框架技能核心笔记,附相关架构及资料
  8. Gephi教程——基本操作
  9. python学习笔记--缓解眼睛疲劳的小工具
  10. 计算机硬盘根目录是什么,硬盘根目录是什么意思?存放哪里?
  11. Mac OS X: 苹果机支持的分区表类型及问题解决
  12. 养生之道——》每天8杯水
  13. MIT 6.S965 韩松课程 05
  14. MHDD修复UNC和TIMEOUT
  15. 小学生体测测试环境怎么填_小学体测在各个学校展开 最新六年级测试项目及评价标准表一览...
  16. mysql中declare语句用法详解
  17. 趁着双11,写个京东商品自动下单
  18. PB控件属性之Graph
  19. Javascript 获得当前文件的url 目录,不含文件名
  20. 数据分析应有的逻辑思维及分析方法

热门文章

  1. SpringBoot进阶教程 | 第四篇:整合Mybatis实现多数据源
  2. Android在string.xml中定义html文档并加载显示,以及拦截WebView链接事件
  3. php取json子对象属性,PHP json获取相关对象值
  4. matlab malloc,[原创]Matlab 高性能代码编写(三)内存是要先分配再使用的
  5. SOA技术相关介绍(RPC, Web Service, REST,SOAP,JMI)
  6. Spring boot Rabbitmq 示例
  7. 中专计算机系专业总结范文,计算机*的中专生自我鉴定范文
  8. docker compose dns 缓存_Docker深入浅出 | Docker Compose多容器实战
  9. java判断字符串是否包含某个字符串_Bash技巧:使用[[命令的 =~ 操作符判断字符串的包含关系...
  10. 多线程安全小结-可见性(内存屏障,共享变量副本)、原子性、有序性(编译器优化、cpu流水线乱序)