Three pig in scrum

When I started my business with pig and chicken, they planned to open a restaurant to sell ham and egg. At this time, the pig thought for a moment, I used my own meat, and the chicken only used the eggs it gave birth. If my startup fails, I will lose my life, and the chicken can still lay eggs without any impact.

1. Scrum stakeholders

In the scrum method, project stakeholders are divided into two categories: chickens and pigs. chickens is the stakeholders of the project, and some are invested in the project, such as senior leaders and end users, the actual participants of the project are pigs. In the company, we are all peigs, and peigs is devoted to the project, which directly determines the success or failure of the project. In scrum, pigs is divided into three roles: scrum master, product owner, and team. These three roles constitute a balanced tie triangle to promote the progress of the entire project.

2. Three roles (pig)
2.1 scrum master

Similar to PM in traditional project management, but not completely, it undertakes the following sub-roles in the project team:

(1) The conference host is responsible for presiding over four major meetings: planning meetings (iterative meetings), standing meetings, iterative review meetings, and iterative review meetings.

(2) sheepdog: shields external interference from the project team.

(3) Alive Lei Feng: Provides product owners and teams with help to help product owners determine their needs and set priorities, and help the team estimate, decompose, and complete tasks.

(4) diplomat: When someone outside the project team does not understand the work of the project team, he is responsible for explaining and releasing the information of the project team.

(5) COACH: Instruct the members of the project team to do things according to the scrum Principles and Methods. When there is a deviation, he will correct it. If a member of the project team is not familiar with the scrum method, he is going to provide related training.

(6) scavenger: Resolves various obstacles encountered in the project progress. If he is incapable or has resources, he can coordinate other members of the project team to remove the obstacles.

The SCRUM master is not always undertaken by one person. In a team, all Members who are competent and familiar with scrum can act as the scrum master.

2.2 product owner

It is the person in charge of the product, or the person in charge of the requirement. he assumes the following role segments in the project team:

(1) field experts: they are demand-side experts who are familiar with requirements. He knows what the real needs of customers, end users, and other stakeholders for the project are. He is responsible for writing user requirements and maintaining user requirements.

(2) Demand decision makers: they decide which demand is important, which demand is not important, how needs are prioritized, and what needs to be released in a certain release. He is responsible for balancing the relationship between demand, progress and resources.

(3) Demand Lecturer: responsible for explaining the meaning of the requirement to other members of the project team during the project progress and answering questions about the requirement.

(4) Acceptance person: prepares the acceptance criteria for a requirement. After a project team member completes a requirement, the product owner accepts the requirement. After the project team member approves the requirement, the customer can only consider that the requirement has been completed.

The product owner can be a user, customer, Product Planning Department, or development department requirement analyst. The product owner is a role, not a single person. It can be multiple people. However, if there are multiple people, they must coordinate and understand the requirements in a consistent manner. In the mobile payment project team, there is a full-time product manager responsible for planning the needs of the entire project. Of course, there is also a need to cooperate with the business side and the channel side, the product manager and the project leader are responsible for communication and acquisition of requirements.

2.3 team

Is the technical owner and a group of people responsible for implementing the system. In a scrum team, it is recommended that the entire team (including the product owner and scrum master) have no more than 10 members. The team should be a dedicated and versatile team, rather than a team with specialized division of labor, this ensures high team efficiency and easy communication. Generally, team members should be full-time personnel. It is best not to work part-time on multiple projects at the same time. The Team undertakes the following roles:

(1) designers: simple design of the system.

(2) Implementers: responsible for implementing the entire system, conducting unit tests on the system, and building the entire system. This includes developers, testers, and O & M personnel.

In a word, the product owner defines what the project is to do. The SCRUM master ensures how to implement the project from the process, and the team technically guarantees how to implement the project.

Recommended articles:

What should I do if a user says a card?

Http://blog.csdn.net/minidrupal/article/details/24544573

Scrum-morning meeting events

Http://blog.csdn.net/minidrupal/article/details/25547577

Product Manager's daily work

Http://blog.csdn.net/minidrupal/article/details/26092691

Quick verification of product value-MVP (minimum viable product)

Http://blog.csdn.net/minidrupal/article/details/26986885

How to locate products (I)

Http://blog.csdn.net/minidrupal/article/details/29386543

What do users study?

Http://blog.csdn.net/minidrupal/article/details/35841945

Rational Construction of product forms (1) -- Who is the target user

Http://blog.csdn.net/minidrupal/article/details/37767955

 

Author: Andy
Introduction: Web engineer, Project Manager, Product Manager
Sign: What is the difference between being a person without a dream and xianyu?