The last article I have briefly introduced the 10 principles of Less, Less this section we look at the basic elements of the framework, if you are concerned about this series of articles, then I assume that you have been very understanding of the scrum, so I will not introduce the content of scrum too much but focus on the difference between the Less framework and the scrum framework!
1. About team roles
The description of the role part mainly clarifies two points. The first is that multiple teams have and only one product owner is responsible for product planning and management. Although there will be a PO in each team in the role definition of scrum, it is emphasized in Less. A team serves the same product goal, so there is a common product owner who is responsible. Of course, you may have questions. If the team is too large and a product owner cannot take care of it, this is what Less Huge is concerned about We will talk about this part later; the second is about the definition of scrum master. In less, the scrum master can cover 1-3 teams. This is actually the inevitable result after the team-level agile maturity reaches a certain maturity. If the team gradually realizes self-organization and self-management, then the scrum master has the ability and energy to be responsible for a larger scope. You can pay attention to the term "self-management" rather than self-organization in this part. The term self-organization has been used in the old version of the scrum guide, but it has also been revised to self-management in the latest version in 2020. You can see the details. In my previous article on the interpretation of the scrum guide, it seems that Less has a clearer definition of the team and is more advanced than scrum; it seems that less does not have too many roles, so is there a traditional manager role in less? ? There is no description in the scrum guide, but some clarifications have been made in less. The previous responsibilities of the manager are mainly two aspects of what to do and how to do it. What is done now is the responsibility of the product manager, and how to do it is determined by the team. What else can I do? The manager has become an empowering role for the team, that is, using various measures to improve the skill level of the team, provide help and guidance to the team, and may also assist the scrum master to help the team eliminate interference. Of course, we should also pay attention to the fact that the manager is an option and cannot blindly position the manager. If the organization really does not need the support of the traditional manager, just remove it (or transform it into a scrum master).
2. About the workpiece
There are three artifacts in scrum, namely the product to-do list, iteration to-do list, and product increment. In less, a product to-do list is maintained. This is the same as the one mentioned in the previous paragraph. Only one product is responsible People are complementary. In addition, the sprint to-do list should have one for each team. After all, the content in the sprint to-do list is the specific task performed by each team, so this does not need to be unified into a list, regardless of how the team tasks are divided In the end, the product increment should be delivered as a whole, so there is still only one product increment in less, which exists in the dimension of the overall product.
3. About the incident
3.1. Iteration planning meeting
In scrum, the iteration planning meeting is divided into two parts. It is similar in less, but the details will be somewhat different. Specifically, the first part of the iteration planning meeting in less is that each team negotiates with the PO to select each team to be responsible In the second part of the meeting, each team has to plan the tasks of its own team, so it can be carried out separately, but it is recommended to be in a public space, which is conducive to rapid communication of cross-team work content; there must be a key Do not divide high-priority needs of the team and to the same requirements as much as possible should be evenly distributed by priority, in order to avoid a high-priority task of a team and be responsible for the risk of not being delivered on time; 3.2 per day will stand the team in addition to In addition to daily stand-up meetings, scrum of scrums meetings should be held 2-3 times a week as needed. The purpose is to communicate collaboration issues between teams, such as matters that need to be promoted together, and work content that affects each other. In the above, we It has already been said that the scrum master will be responsible for multiple teams at the same time, so the sos meeting cannot be completely dependent on the scrum master. Each team should send representatives to participate. After all, this is also a part of the team’s self-management; are you already here? Realizing a problem is that in less, the team is expected to be relatively mature. It is a feature team and a cross-functional team in order to effectively support the operation of the less architecture. 3.3. Iterative review meeting . The changes to the review meeting Less will be slightly larger, and the team review meeting will be removed directly. Because all teams deliver a common product, the review will proceed together, although the content is still to show the product to the product and the customer Incremental, but the form is expected to be more flexible. It can be a form similar to an exhibition, where you can see the functions of the entire product, and you can also discuss the part delivered by a certain team; 3.4. Iterative review meetingLess's point of view is that the scrum retrospective meeting is still to be conducted, but in addition there is an overall retrospective conducted by all teams, because the focus of the two meetings will be different, and the overall review focuses more on cross-team collaboration issues and all teams Common mechanism issues, so the participants should include product owners, scrum masters and team representatives; this article mainly introduces the roles, artifacts and events of less. I believe everyone has a preliminary understanding of less, and we will come to the next article Take a look at the changes in less huge!
