What is Scrum？
Overview of the Scrum
Agile is a methodology system, within this large system there are many branches, each branch has different emphasis or responsibility, some focus on research and development management, some focus on engineering practice.
Scrum: is a framework of management practices within the Agile system.
The Scrum characteristics
SCRUM 核心概念: 重视人与人之间的沟通问题和资讯传递问题。团队人员需要共同协作，为了一个共同的目标而做出努力。在英式橄榄球列阵争球中它需要搭配大量的战术配合应用。因此这个管理制度用scrum来命名。
Scrum: It absorbs the essence of short rugby game time, with short iteration cycle. Meetings are short and concise.
The line of scrimmage in rugby.
The core concept of Scrum is to focus on interpersonal communication and information transfer. Team members need to work together and make efforts toward a common goal. In rugby line-up scrum it requires a lot of tactical application. Hence the name Scrum for the management system.
Scrum comes to China: someone translates it as mahjong
It has four distinct features.
Self-organized team. Mayou comes from all over the world and never arrives late, regardless of wind or rain.
They all have a clear goal, the purpose is only one, to play mahjong to make themselves happy, so that the owner of the mahjong shop to make money.
Everyone is very concerned about their upstream and downstream, concerned about the upstream card can eat, concerned about the downstream card can not touch, concerned about the opposite card can not hu.
There is reflection and review. On the way home, poker friends are kind like brothers and sisters, telling which hand is not good today, and how to improve it tomorrow.
what is Scrum 3355？
3个角色 3个工件 5个仪式 5个价值观
3 roles 3 artifacts 5 rituals 5 values
A team has three roles based on who participates in a thing, three artifacts based on what these roles work together and what they deliver, and five rituals based on what process the team follows to carry out work on the basis of the artifacts. And what kind of principle culture does the team work according to, these are the five values. So what are all of these? Let's talk about 3355
Responsible for the creativity and highlights of products.
Define the characteristics of the product.
Answer requirements questions from the team.
Scrum Master: SM for short, he is the service leader of the team
Responsible for helping the team to eliminate obstacles and complete related work. This includes organizing daily meetings, as well as other support and assurance work.
But he doesn't get to decide what the product will look like. He doesn't get to decide the budget or the personnel.
Team: The Team is made up of developers, testers, and others who help with development
Usually, the number of team members is set at 3-9. Why? He's not a team with less than three people. The cost of communicating with more than 9 people is too high, so it is set at 3-9 people.
Team members should be versatile and often take on multiple roles. Sometimes the developers do the testing, and sometimes the testers write the documentation, but in either case the team needs to collaborate and work together to get the product out.
Product Backlog: 产品负责人先从众多的User Story中,筛选出优先级较高的，并把它们放到Product Backlog列表中。这个列表会随着每次Sprint的执行情况和用户的Feedback进行更新，Product Backlog中出现的条目是User Story,它是表述产品特性的一种方式，典型的条目格式是:作为一个用户角色，我想要什么功能，以便获得什么价值。PO通过User Story来了解需求的细节，从而为Scrum团队合理的排列Story的优先级，优先级高的Story将进入到下一个短冲 Sprint Backlog，即迭代待办列表。
Product Backlog: The Product owner first selects the highest priority User stories from the numerous User stories and puts them in the Product Backlog. The list is updated with each Sprint and the User's Feedback. The entry in the Product Backlog is the User Story, which is a way of expressing the Product's features. The typical entry format is: as a User role, what functionality do I want in order to get value. The PO uses User Story to understand the details of the requirements to prioritize the stories for the Scrum team. The stories with the highest priority will be placed on the next Sprint Backlog, the iteration Backlog.
Sprint Backlog: 是Product Backlog的一个子集。在一个Sprint开始的时候，团队会从Product Backlog中选出优先级高的User Story，生成新的Sprint Backlog，在这个Sprint过程中使用。
Sprint Backlog: A subset of the Product Backlog. At the beginning of a Sprint, the team selects the User Story with the highest priority from the Product Backlog and generates a new Sprint Backlog to be used during the Sprint.
Product Increment:他是一个Sprint 完成的 潜在的 可发布的产品的组成部分。在Sprint最后，新的增量必须是完成的，这意味着它必须能用，而且达到了Scrum团队定义的完成标准。无论PO是否决定对当前的Increment进行发布，这个Increment必须达到可发布的状态。
Product Increment: This is a component of a potential releacable Product completed by a Sprint. At the end of the Sprint, the new increment must be completed, which means it must be usable and meet the completion criteria defined by the Scrum team. Whether or not the PO decides to publish the current Increment, this Increment must be in a publishable state.
Sense of ceremony
The sense of ritual is what makes one day different from other days, one moment different from other moments, and there are rituals in agile development as well
Feeling. Agile draws lessons from the concept of lean visual management and forms a visual tool with its own unique style - Kanban. Kanban is the guarantee of soft in agile development
Continuous integration, visual tools that don't overload development teams. In agile projects, team members move cards to indicate the status and progress of tasks
To strengthen the sense of ritual at the beginning and end of tasks. Before the start of the iteration, the tasks in the iteration will be estimated to ensure that the planned workload is relatively reasonable
Enhance a sense of ritual Agile teams often use Agile Estimate playing cards to make time estimates. These meetings shall be held at fixed times and places to ensure that members attend the meetings
Mood preparation and expectation. In Agile meetings, team members speak one by one, and only those who are actually involved in the project have a voice.
The short dash can end with a hearty meal to celebrate the smooth delivery of the product. The sense of ritual means that the team gradually determines specific habits of action according to its own culture and the size of its members, so as to enhance the tacit understanding, maintain discipline and improve work efficiency.
After each meeting, the team may not realize the end immediately due to inertia, and will still be immersed in the previous work atmosphere, which will weaken the sense of ceremony and cause low morale in the follow-up work. Therefore, the use of the closing phrase to end the meeting.
Product to do list refining meeting
Product Backlist Refining Sessions: Find a time during a Sprint to refine the product's functional requirements from a user's perspective, away from the developer's point of view.
The Sprint plan will
第二个阶段则是将这个短冲做一个工作的拆项，由团队去决定他们要怎么进行分工。 通常PO不一定会参加这 个会议。
计划会议的意义是让团队共同确认和理解本次sprint要成的工作，参与本次sprint的所有人都要参加，计划会议第一步是产品负责人向团队成员详细讲解每一个user story，与会人员应认真听产品负责人的讲解，以确保自己对每一个story的理解都是正确的。讲解后并对userstory 进行排序估算。团队集体参与。最终制定出这一期要完成的story 列表，即sprint backlog。我们在分析用户故事时要清楚用户的根本需求，从而制定最佳解决方案，问题的最优解往往要考虑投入产出比。sprint backlog的制定是整个scrum团队基于自身情况，共同商讨的结果。而不是产品负责人自己独裁决定的。sprint backlog制定出来后，下一步就是要对story进行任务分解和领取。
The short punch planning meeting was divided into two stages:
In the first stage, the Product Owner should inform the team what functions should be completed in the short burst and how to complete the short burst.
The second stage is to turn the project into a work item, and let the team decide how they want to divide the work. Usually the PO will not necessarily attend this meeting.
The meaning of the planning meeting is to let the team jointly confirm and understand the work to be accomplished in this sprint, and all the participants of this sprint should attend. The first step of the planning meeting is that the product owner explains each user story to the team members in detail, and the participants should listen carefully to the explanation of the product owner. To make sure you understand each story correctly. After the explanation, sort the UserStory and estimate it. Team participation. The result is a list of stories to be completed for this period, known as the Sprint Backlog. When we analyze user stories, we need to understand the fundamental needs of users, so as to develop the best solution. The optimal solution to a problem often takes into account the input-output ratio. The development of the Sprint Backlog was a collaborative effort by the entire Scrum team. Not the product owner's own dictatorial decision. With the Sprint Backlog in place, the next step is to break down and claim the Story.
After confirming the Sprint Backlog, the second part of the planning meeting is for the team to break down and claim tasks for each story. The criteria for decomposition is to break down all the tasks that the Story does, including development and non-development tasks. After the task decomposition, people get their favorite tasks from resources and complete the time estimation. Finally, there is a clear person in charge for each task. Attention should be paid to the principle of free and voluntary acceptance of tasks. Instead of being assigned by the project manager. Why take it freely and not be afraid of overestimation by team members?
Developers are free to receive and estimate, which is a commitment to the team.
There is a consensus on the size of the task, plus healthy competition, so you are not afraid to deliberately overestimate the hours.
Timely synchronize the information to ensure the openness and transparency of the information.
With the help of JIRA software, dynamic burn down chart and other functions, timely understand everyone's work situation.
Set a time for each day and tell the team what they accomplished yesterday. What you need to accomplish today, what difficulties you encounter, how do you need help from others, usually because you don't want to last too long,
That's why standing is used to avoid people sitting too long, too comfortable, too long discussion.
The Sprint review
Sprint Review Meeting:
A rush ends with a feature output, so all stakeholders including the customer, the boss, and the end user are invited to review the result of the feature. If the feature is not what the customer wanted, the loss is only 1-2 weeks. Rather than months of hard work.
Sprint retro meeting
Usually, only Team and SM participate in this meeting, and the supervisor is not allowed to attend. Avoid supervisor interference in discussions that affect the team's autonomy.
Let the team review this short rush, where did not do well, where need to strengthen, how to improve next time, the action measures to record, continuous improvement
The five values of Scrum
Scrum has five values and concepts
Team members commit to achieving the team's goals
Have the courage to stand up for what is right and deal with tough problems
Everyone is focused on work and team goals
All the work and challenges are made public
Team members are competent and respect each other.上一篇 搜索 下一篇