Unveil scrum’s Secret in 7 minutes (scrum framework)
What is scrum
Scrum is a framework for developing and continuously supporting complex products. This includes scrum’s roles, events, artifacts, and the rules that organize them together
Scrum (noun): scrum is a framework in which people can solve complex adaptive problems while delivering as high value as possible efficiently and creatively.
- Easy to understand
- Difficult to master
Scrum is a process framework that has been used to manage the development of complex products since the early 1990s. Scrum is not a process or a technology for building a product; rather, it is a framework in which you can use a variety of different processes and technologies. Scrum makes the relative effectiveness of your product management and development practices clearer, so you can improve them.
From the scrum guide, we can quickly summarize as follows:
- Scrum is a process framework
- Scrum framework for developing complex products
- Scrum framework helps people solve complex adaptive problems
- Scrum can help people deliver as high value products as possible efficiently
- A variety of different processes and technologies can be used in the scrum framework
Therefore, Ken schwaber once said:
Scrum is like your mother-in-law, constantly pointing out your problems.
It is not difficult to see that the core of Scrum framework is to constantly expose problems. That is, it is a feedback framework that exposes problems.
Let’s take a look at what is included in the scrum framework.
Scrum framework is 3 roles, 3 artifacts, 5 events, 5 values (i.e. 3-3-5-5)
The three roles of Scrum are:
- Product owner. The product owner is responsible for maximizing the value of the product and development team work. Bear the ultimate responsibility for the products and have the right to live and kill. The product owner can decide what to do first and then.
- Development team. The development team includes a variety of professionals responsible for delivering potentially releasable and “completed” product increments at the end of each sprint. Only development team members can create increments. The development team mentioned here is different from what we usually say. there
developmentIt’s about product development, not writing code. Then the development team will be a self-organizing cross functional team.
- Scrum Master。 Scrum master is responsible for promoting and supporting scrum as defined in the scrum guide. Scrum master does this by helping everyone understand scrum theory, practice, rules, and values. This character has no Chinese translation. But he is by no means a project manager, nor is he
team leader。 Scrum master is more like a team coach.
- Product backlog. The product to-do list is a sequential list, which contains everything possible for a product, and is the only source of product demand changes. The product owner is responsible for managing the content, availability and sorting of the product to-do list.
- Sprint to do list. A sprint to-do list is a set of product to-do list items selected for the current sprint, plus plans to deliver product increments and achieve sprint goals. The sprint to-do list is the development team’s forecast of what functions will be required for the next product increment and the work required to deliver those functions to the “done” increment.
- Increment. Product increment is a synthesis of all product to-do list entries delivered by the development team within sprint. The increment must be a definition of done that meets the team’s definition
Sprint。 Sprint is the core and container of scrum. A sprint is a time box (fixed start and end times), and the next sprint follows the previous one, with no pause in between. Sprint consists of sprint plan, daily exhibition, sprint execution, sprint review and sprint review.
Sprint program. All the work to be done in a sprint is done in the sprint planning meeting. The plan was completed by the entire team (product owner, Scrum master, and development team). There are two main tasks of sprint plan:
- What product to-do list entries are to be completed in this sprint? （What）
- How do you complete these items? （How）
Daily station meeting. An event in which the development team synchronizes progress for 15 minutes and adjusts daily. At the daily station meeting, each team member answers the following three questions (basic, new questions can be added according to the situation)
- What did I do yesterday to help the development team achieve sprint goals?
- What am I going to do today to help the development team achieve sprint goals?
- Are there any obstacles that hinder me or the development team from achieving sprint goals?
Sprint review. At the end of sprint, the scrum team together reviews the product increments delivered, andadjustmentProduct to do list. The sprint review is not a sprint demo or a sprint demo. Be sure to include feedback collection and adjustment.
Sprint review. Scrum team reviews and adjusts work methods, processes, and continuous improvement events. The main purpose of sprint review is to:
- Review the previous sprint about people, relationships, processes and tools;
- Identify and rank the major areas that are well done and potentially need to be improved; and,
- Make plans to improve the way scrum teams work.
Product to-do list sorting (refinement). That is, demand carding meeting. Every week the scrum team gets together to prepare for the next sprint.
Scrum’s five values are:
When the five values of commitment, courage, focus, openness and respect are practiced and internalized by the scrum team, the three pillars of Scrum transparency, inspection and adaptation become reality, and trust is built between everyone. Scrum team members learn and explore these values through scrum events, roles, and artifacts. The success of Scrum depends on people becoming more proficient and practicing the five values. People are committed to achieving the goals of the scrum team. Scrum team members have the courage to do the right thing and deal with tough issues. Everyone is focused on sprint and scrum team goals. The scrum team and its stakeholders agreed to make all work and implementation challenges public. Scrum team members respect each other and become more capable and independent people.
The core content of Scrum is from the scrum guide. Here is a 7-minute video, which is a good overview of 3-3-5-5 in scrum framework
The whole scrum framework is interpreted according to the lifecycle of product development (software as an example).
Station B video
This article starts from Bob Jiang’s blog. Please contact Bob Jiang for reprint