Backend Developer Learning Agile Requirements --> Stakeholder Analysis and Identification

Stakeholder analysis and identification

5W1H Stakeholder Analysis and Identification

1. What are the stakeholders?

1. People and organizations that directly or indirectly influence the topic, as well as those that are influenced by the topic, and users are also stakeholders, being direct or indirect users of the product

2. Also known as stakeholders, individuals or organizations that are actively involved in the topic or whose interests may be positively or negatively affected in the topic

2. Why analyze and identify stakeholders?

1. Identify the people or organizations that have a significant impact on the topic or product and obtain their expectations and needs for the topic or product

2. Identify the core stakeholders, decision makers, proponents, and actual users, and focus on meeting the needs of the core stakeholders to facilitate the project.

3. There are system supporters as well as system beneficiaries, and understanding of how stakeholders collaborate with each other

4. Analyze and understand stakeholder information in preparation for user research and further work

5. Analyze and control the priority of requirements, reduce the conflict of interest between stakeholders, help designers to set product direction, goals, and ensure the realization of the product.

3. Who, at what stage and in what scenario to use it

It's a generalized mindset that is not limited to software engineering and can be used by all, for example:

1. Product managers, in the requirements analysis phase, need to understand the needs and expectations of their stakeholders, as well as the collaborative relationship between stakeholders, aligning goals and reaching consensus

2. Product managers, in the preparation phase of user research, need to understand the user's information and develop a plan for interviews

3. Developers, in the requirements realization phase, need to define the user roles, their responsibilities, and the collaboration relationships

4. The project manager, during the advancement phase of the project, needs to find the decision makers and managers of the project, understand the relationships, assess their level of influence on the project, and figure out how to push the

4. How it is used

1. How to identify stakeholders

1. Identify by organizational structure, function, and position
   • Organization chart of the company
   • Departmental personnel, job functions
   • Nail, WeChat
2. Identify by participant, participant
   • Purchaser, Consumer
   • Collaborators, supporters
3. Identification from Stakeholder Interviews
   • Identify from stem communication, e.g. who is in charge of finance ......
4. Documentation, Business Processes, System Roles
   • Business Flow Chart
   • User role relationships on the system

2. How to analyze stakeholders

1. Analyzing Interests

   Analyze the benefits available to the stakeholders and prioritize themcruxStakeholders' interests.

   1. What benefits, value does the design bring to the user
   2. What problem can be solved for the user

2. Analyzing negative impacts

   The project or product is designed to be used in a way that may harm some of the interests of the stakeholder, such as increased workload for the stakeholder, reduced income, privacy breaches, etc.

3. Analyzing expectations/goals

   In order to obtain the benefits in the project, the stakeholders will put forward requirements on the project, including product requirements, expectations or personal values (usually the stakeholders' views on the project's aesthetics, fees/free, fairness, etc.), analyzing the expectations/objectives of stakeholders is a key point to grasp the content and direction of product design, prioritizing the expectations and objectives of the core stakeholders to a certain extent determines the success or failure of the product.

4. Analyze how stakeholders collaborate with each other and the roles of stakeholders

   1. proposer
   2. Direct user of the requirement, the originator of the requirement, not necessarily the business user, needs to identify the actual user of the business
   3. People affected by demand
   4. Analyze how stakeholders collaborate with each other

5. Clarify the importance of stakeholders

   1. Some stakeholders make or break a project.
   2. Some stakeholders have little use and involvement

6. Clarify the business impact of stakeholder needs

   1. People who actually use it, generally make demands from the point of view of their own use
   2. People who manage the business and make demands from a management and operational point of view

3. How to identify core users

1. according toOperational indicatorsSegmentation of users, such asFrequency of use, impact size, duration of use, number of purchases
2. When there are many stakeholders, you can use a user map to visualize the users.

4. Outputs and organization, stakeholder maps

1. The largest group of users who do not have an explicit choice of medical practitioner
   • The frequency of use is on the high side, the use of time is on the long side, the platform information to help users quickly locate, hospitals, departments, doctors, to provide disease popularization, to help understand the basics of knowledge
2. surgeon
   • Check out some hospital-related information, statistics on your profile and browsing information, as well as feedback.
3. Informed users
   • Understanding and collecting information about hospitals in Chengdu, or information about disease-related information
4. Elderly autonomous users of medical care
   • User groups are small and most older persons are accompanied by their children
   • Considering the presentation and reading of information for older users

The more inner-circle users, the more core