Shulou(Shulou.com)06/03 Report--

Introduction:

After opening the Sprint Setup Meeting and making a reasonable estimate of all the Story Point, the next step is to subdivide the story into the hands of each developer / tester and let them build a sub-task under the story. The key question here is how to make more efficient use of the team's human resources and make the most reasonable allocation.

Implementation method:

This is actually based on skill set, because as we all know, the level and experience of a team are uneven, there are senior / intermediate engineers, experts in this field, and some are good at another field.

So when our team was founded last year, the first thing we did was to collect everyone's skill set. Thus team leader can better understand each person's strengths and weaknesses, thus assigning tasks more scientifically.

A skill set is often an excel form, which shows my skill set (partial) here.

After having everyone's skill set, I will make a reasonable task allocation according to the situation of the team. If the Sprint estimates a lot of total story point and the team will be very busy, then I will try my best to assign tasks according to skill set and assign story to the people who are the best in the field to do it to reach the speed limit. If the Sprint estimate is not very busy, then I will let you choose the story and try to do what you are not good at, so that you can more effectively improve the overall combat effectiveness of the team, and you can learn from each other and improve together.

After allocating all the story, I will ask the team to build their own sub-task under the story they are in charge of and estimate the time, which is for the developer to estimate, because only he has a reliable understanding of his own speed, and the results estimated by others are meaningless to him. In fact, this time should not be too accurate, as long as it is not too outrageous. (don't look like the 10-hour difference in the js check estimate of a form on a page.) then after everyone has established the sub-task, the module manager and I will review each sub-task in turn.

Summary:

(1) assigning story to everyone is suggested to be determined according to the progress of skill set and sprint. If there is plenty of time, try to allocate people to do modules and areas that they are not good at, to achieve the role of exercise and team building. If time is tight, try to allocate according to the highest skill set to ensure that the project is delivered on time.

(2) the establishment of a sub-task must be timely, and it is best to build it immediately after the story is confirmed, rather than waiting for the story to start, so as to ensure that the burn down chart looks good, and these sub-task must be specially assigned to ensure that their time estimates are reasonable under the review.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.