In the interests of SCRUM methodology in the project stakeholders divided into two categories: Pigs and chickens role role, pigs is the actual participants in the project team, chickens external project team personnel, including managers, end users, and so on. Pigs scrum subdivided in three roles: the role of the status of Scrum master, Product owner, Team, three peer constitute a balanced triangle promote the progress of the entire project.
Scrum master is not a project manager, he has no power to assign tasks, and no power of assessment, has no power to command, he assumed the role of subdivision project in the following groups:
(1) Meeting Moderator
He chaired four major conferences: the planning meeting, daily stand up meetings, review meetings iteration, iteration retrospectives.
(2) Collie
He is responsible for the project team shielded from external interference.
(3) Lei Feng
He gave product owner, team help, help determine product owner needs, prioritize, help team make estimates, break down tasks to complete the task.
(4) diplomats
When someone outside the project team do not understand the work of the project team, he is responsible to the explanation, the project team responsible for the information released.
(5) Coaching
He directed the members of the project team in accordance with the principle of doing SCRUM, methods things, when deviations, to correct him, can say that he is the spiritual godfather, who is also the police (QA). If there are members of the project team are not familiar with SCRUM approach, he was going to provide related training.
(6) scavenger
He is responsible to remove all obstacles in the progress of the project, if he did not have the capacity or resources he can coordinate with other project team members together to remove obstacles.
SCRUM master. Not fixed borne by one person or in a team, we have the ability, familiar with SCRUM members can play a SCRUM master.
Product owner is responsible for the product, or to say what is the person in charge needs, he assumed the role in the project team following breakdown:
(1) experts
He is an expert in the demand side, demand familiar. He knows customers, end users, and other stakeholders on the real needs of the project is what it is. He is responsible for the preparation of user requirements, maintenance needs of the user.
(2) the needs of decision makers
Which needs important, not important which needs, prioritizing the needs of how, in a release in which demand is to release him finalized. He is responsible for the balance between demand, schedule and resources.
(3) demand lecturer
Meaning he was responsible for the other members of the project team needs to explain the progress of the project process, the needs answering.
(4) Testers
He is responsible for the preparation of each requirement of acceptance criteria, functional test cases.
(5) Acceptance people
When the project team members to complete a requirement, it is the product owner for functional testing, acceptance, approval he needs to think a complete.
Product owner can come from the user, the analyst customers, sales, product planning department or a development department, whether it is from what is required to meet the following requirements:
(1) Collaborative: easy collaboration, ease of communication;
(2) Representative: Representative, to represent users, customers, the interests of the market;
(3) Authorized: an authorization, has been authorized users, customers, markets, and have decision-making power on demand;
(4) Committed: responsible, able serious, conscientious work;
(5) Knowledgeable: line, understand, familiar with the requirements;
More than five requirements can be abbreviated as CRACK, this is our ideal, to find such a product in the real owner with some difficulty.
Product owner is a role, it does not mean that a person may be more than one person, but if more than one person, which is more than one person should be coordinated, understanding and interpretation of the requirements are the same.
Team is responsible for technology, they are responsible for implementing this system, they are self-managed, it does not require external managers to manage them. In a SCRUM team, in general, the entire team (including product owner, scrum master) no more than 10 people, team-rounder should be multi-skill player, not the kind of specialization of the team, so as to ensure the team more efficient, but also easy to communicate. Team members generally should be full-time staff, part-time can not do multiple projects at the same time. team took on the role of the following breakdown:
(1) Designers
The system is designed to be simple.
(2) implementer
Responsible for the whole system, and the system performs unit testing, build the entire system.
(3) management staff
Everyone will work together to estimate, select the task together, work together to track progress.
Product owner defines what the project, Scrum master how to ensure the realization of this project from the process, Team ensures technically how to achieve this project.
----------------
Original link: https: //blog.csdn.net/dylanren/article/details/6939680