background
In the lower die traditional development mode, send tasks assigned by the project manager to individuals, but in agile development, the task of the project manager is assigned to the individual, and in the agile development of business team entitled. Many enterprises development tasks when there are several task-claim in how to do? Q: " planning meeting unclaimed development tasks when there are several tasks unclaimed how to do? "
problem analysis
First, with respect to the tasks assigned to develop the traditional development model, we need to know why agile development is to receive the task. In agile, whether Agile Manifesto or Scrum Guide , do not assign (assign) the word, but the use of the term "self-organization", as follows:
- Best architectures, requirements, and designs emerge from self-organizing teams (12 Agile Manifesto Principles)
- Self-organizing teams choose how best way to complete the work, rather than by people outside the team to guide (Scrum Guide)
- They are self-organized. No one (even the Scrum Master) should have the right to tell how the product development team to-do list becomes a function increment (Scrum Guide) potentially publishable
So what "self-organization" is it?
From the literal meaning to understand, "self-organization" is this: arrangement dispersed people or things to make sure people with systemic or whole, is to arrange themselves. In agile development, self-organizing teams that have self-management, self-driven, agile development teams the ability of self-learning itself, such teams typically have the following characteristics:
- Team members themselves "pull" work, not passively wait for their leader assigned work;
- The team as a whole to manage their work;
- The team is still in need of counseling and guidance, but does not require command and control;
- Team members communicate with each other in close exchanges;
- Team proactively identify and ask questions, and common solutions;
- Team continue to improve their skills, encourage exploration and innovation.
More details about "self-organization" is not within the scope of this FAQ, please see as more interested in literature.
From the Agile Manifesto and Scrum Guide on the work on the task of view, in our practice agility when play was the main development team's own initiative, controllability change from the original development team became self-organization, and development tasks it becomes a collection from the original assignment. The advantage is that, to receive the task is to play the people's initiative, and autonomy is one of the people in power and creative problem solving, good self-organizing teams and individuals to give high performance and excellent results of the work and love work environment. In addition, everyone is the best understanding of their own, they are also good for their assigned tasks, compared with the traditional development tasks assigned brought Yi subjective, improper distribution more reasonable.
Then return to "planning meeting unclaimed task, there are several tasks unclaimed how to do?" On this issue. But before this, you need to clarify a point of view is that, in planning the meeting, does not have to collect all the complete development tasks. In the Scrum Guide states that "the work needed to receive the Sprint planning meeting and during the Sprint." During this period, can be understood as the daily Scrum meeting the target based on station to receive tasks. In addition, Mike Cohn also said before, is not recommended to receive development tasks in planning a meeting, this may result in changes to the target by a team of individuals, and thus contrary to the intention of agility, reduces flexibility. Please refer to Appendix "Should Team Member Sign Up for Tasks During Sprint Planning?". In general, the development task no reason unclaimed are:
- Development tasks difficult : when development tasks are more difficult to solve, beyond the capacity of most of the members of the team, team members worried that there may be overtime, even the case, "996" is reluctant to claim.
- Development tasks of range : When the task is beyond content development team members to master the range, such as Android will not IOS, development will not be testing, it may appear "I want to claim, but it does not allow instances ah" Happening.
- Fear of others accusations : there is work content can be challenging, worried that he did not do a good job, leading the team failed to reach the target and blame.
Solving program
In an agile Scrum team, Scrum Master plays an important role, the role of a part of the role is to help the team to become self-organizing type team, so that the team can adopt a positive attitude to face the sprint of development tasks. In addition, when the task appears no one wants to claim the case, the first Scrum Master should help the team figure out the reason no one claimed what then prescribe the right medicine, the following three cases based on the analysis of the solutions were given.
Development task difficult
For large development tasks difficult situation, Scrum Master should organize an effective team task decomposition, using probes Spike technology, to explore solutions to reduce the difficulty of the task, and then by the team to claim the ( more about Spike interpretation See Appendix ) . Or to encourage technological capability and technology than the average member of a large cattle through pair programming along the way to claim the task ( more on interpretation of the knot programming see Appendix ) . Huawei cloud DevCloud may be difficult for the large class of user by way of the sub-story split work item, while in the basic information provided by carbon copy process and the manner of pairing junction recording programming staff, following Fig.
In addition, the daily Scrum when the station will , to pay attention to and understanding of the development tasks, the risk assessment, if the problem in time to help coordinate and solve problems. In the review meeting , to deal with the situation of the class to analyze and can output a standard set of team-based work methods, and then the solution record in team knowledge base, Huawei cloud DevCloud provides Wiki functionality can be good for the team finishing and recording mode, as shown below.
Development tasks of range
Agile advocate team is cross-functional teams, cross-functional teams but does not mean that the individual can do all things, we hope to cross-functional teams are often made to master a number of skills T personnel (each member in a professional field It has the depth, breadth has in other areas ) thereof. Well first, you need to Scrum Master can and team organize and maintain members of the technical matrix, the personal skills to grasp the situation of the team public (know what team lacking, know who's available science, etc.), and then regularly organize technology sharing and other activities to help team members learn (mainly in share mode after learning a new technology), so you can upgrade to a certain extent, members are willing to receive other tasks in the sprint passion (finished school course, I want to use it slightly). It is also possible by the expertise of the team members and the members will, using pair programming way to receive the task to achieve the expansion of personal technology. Team members of the T -type capacity building not only allows the team to receive the task when there are more choices, but also provides members of backup capacity, reduce unclaimed situation occurs. In addition, also we need Scrum Master pay attention to daily assess risk and guide the team review the matter and maintenance team knowledge base.
Fear of others accusations
There is a certain challenging work content, worried that he did not do a good job, leading the team failed to reach the target and blame. Scrum Master should carry out the team as a whole team of thought, and guidance and emphasis on Scrum values , respect for every member of the team's background, experience, of course, including the selection of development tasks, but also encourage members to have the courage to choose and try. In the actual work, we can be on the wall, whiteboard, etc. affixed slogans (such as " respect for others " , " only team not individuals ," etc.), which allows the team to shift in terms of the ideology, slowly dare to receive challenging task. In addition, Scrum Master to fully protect the members of the enthusiasm for challenging work unclaimed. For example, to prevent the situation accusations and criticism in the review meeting, review and summarize the focus should always be ways of doing things rather than people and harsh accusations.
to sum up
These three cases no one claimed the task, is more common. But in the real practical project, the situation of each company or team are not the same, can not exhaustive of all, it should be specific conditions. For example, when a company's primary concern is the survival of the problem, and just such a quick transition team in receiving development tasks may be more biased in favor of the half assigned to receive half way, as if the FAQ "from the perspective of agile management to He said the team is actively claim the task good or good distribution through administrative tasks "mentioned, when the team agile maturity level is low, the first by the team can claim the leadership let control. This is like the Chinese economy as " market-oriented economy, appropriate macro-control " . But regardless of this " regulation " how efforts, we should encourage team members to proactively receive the task , and with the progress of the task flexibly adjust in a timely manner to control the risk, when necessary, the need to coordinate aid from other sources or related to the leadership to intervene to ensure that the target is not affected iteration.
Refer to Appendix
Should Team Member Sign Up for Tasks During Sprint Planning?
